Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 7.843971252441406e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0006973743438720703s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.3258657455444336s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.738926887512207s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00038909912109375s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 6.4373016357421875e-06s
INFO | --- Analysis for 0080-3626 took 6.5074403285980225s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.506111145019531e-05s
Availability | VoID file availability check for 土地利用图 took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.2582836151123047s
Reputation | Calculation of the PageRank for 土地利用图 took 0.020097732543945312s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.956390380859375e-05s
Believability | Calculation of trust value for 土地利用图 took 6.198883056640625e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 4.195763826370239s
Availability | SPARQL endpoint availability check for 113322 took 5.030632019042969e-05s
Availability | VoID file availability check for 113322 took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for 113322 took 0.7099218368530273s
Reputation | Calculation of the PageRank for 113322 took 0.020000696182250977s
Interlinking | Calculation of Degree of Connection for 113322 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for 113322 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.8371810913085938e-05s
Believability | Calculation of trust value for 113322 took 5.4836273193359375e-06s
INFO | --- Analysis for 11 took 5.081634759902954s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.315376281738281e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2791311740875244s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.0200042724609375s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.956390380859375e-05s
Believability | Calculation of trust value for Korepetycje Buki took 6.9141387939453125e-06s
INFO | --- Analysis for 12323 took 2.8483896255493164s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.06643819808959961s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00020885467529296875s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2641565799713135s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.019959688186645508s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.654594421386719e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.0251998901367188e-05s
INFO | --- Analysis for 2000-us-census-rdf took 2.422112226486206s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 1.755518913269043s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2636425495147705s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020146608352661133s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.743171691894531e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 4.76837158203125e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 5.868102073669434s
Availability | SPARQL endpoint availability check for Open Data Web took 0.36908698081970215s
Availability | VoID file availability check for Open Data Web took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2722282409667969s
Reputation | Calculation of the PageRank for Open Data Web took 0.020052671432495117s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.3855438232421875e-05s
Believability | Calculation of trust value for Open Data Web took 5.7220458984375e-06s
INFO | --- Analysis for _data.odw.tw took 2.737067699432373s
Availability | SPARQL endpoint availability check for 土地利用 took 4.291534423828125e-05s
Availability | VoID file availability check for 土地利用 took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2722434997558594s
Reputation | Calculation of the PageRank for 土地利用 took 0.02003955841064453s
Interlinking | Calculation of Degree of Connection for 土地利用 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.8848648071289062e-05s
Believability | Calculation of trust value for 土地利用 took 5.4836273193359375e-06s
INFO | --- Analysis for _data1.odw.tw took 2.4130795001983643s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.4345855712890625e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.29829931259155273s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.86102294921875e-05s
Believability | Calculation of trust value for 土地利用模型 took 6.4373016357421875e-06s
INFO | --- Analysis for _data2.odw.tw took 5.026638507843018s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.267692565917969e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.000576019287109375s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.24958515167236328s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020072460174560547s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8371810913085938e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.7119743824005127s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.1961669921875e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.31150293350219727s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.022156715393066406s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0010733604431152344s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.910064697265625e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 7.3909759521484375e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 27.361339569091797s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.220008850097656e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.26859068870544434s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.8371810913085938e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 4.5299530029296875e-06s
INFO | --- Analysis for A1 took 2.762977361679077s
Availability | SPARQL endpoint availability check for SummerOlympics took 1.150402545928955s
Availability | VoID file availability check for SummerOlympics took 0.0003349781036376953s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2629432678222656s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02029109001159668s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.246566772460938e-05s
Believability | Calculation of trust value for SummerOlympics took 6.198883056640625e-06s
INFO | --- Analysis for abc took 6.269334077835083s
Availability | SPARQL endpoint availability check for Test_m took 4.2438507080078125e-05s
Availability | VoID file availability check for Test_m took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Test_m took 0.24869036674499512s
Reputation | Calculation of the PageRank for Test_m took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for Test_m took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.337860107421875e-05s
Believability | Calculation of trust value for Test_m took 6.198883056640625e-06s
INFO | --- Analysis for ABC took 2.2614665031433105s
Availability | SPARQL endpoint availability check for my intro took 4.2438507080078125e-05s
Availability | VoID file availability check for my intro took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for my intro took 0.2535409927368164s
Reputation | Calculation of the PageRank for my intro took 0.02036309242248535s
Interlinking | Calculation of Degree of Connection for my intro took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for my intro took 2.7179718017578125e-05s
Believability | Calculation of trust value for my intro took 5.9604644775390625e-06s
INFO | --- Analysis for abhay_intro took 2.262580156326294s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.3414647579193115s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00021314620971679688s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.2651495933532715s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02028346061706543s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.846687316894531e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for abs-linked-data took 2.603562116622925s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 5.269050598144531e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.28887104988098145s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.02028346061706543s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.7179718017578125e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.239776611328125e-05s
INFO | --- Analysis for academic-offer-of-unl took 2.86259126663208s
Availability | SPARQL endpoint availability check for AcadOnto took 4.1961669921875e-05s
Availability | VoID file availability check for AcadOnto took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.25870680809020996s
Reputation | Calculation of the PageRank for AcadOnto took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.8133392333984375e-05s
Believability | Calculation of trust value for AcadOnto took 7.152557373046875e-06s
INFO | --- Analysis for acadonto took 3.979590654373169s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.341197967529297s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.26890087127685547s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.019951820373535156s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.1961669921875e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 5.245208740234375e-06s
INFO | --- Analysis for acorn-sat took 35.21421408653259s
Availability | SPARQL endpoint availability check for Addgene took 4.172325134277344e-05s
Availability | VoID file availability check for Addgene took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for Addgene took 0.2777581214904785s
Reputation | Calculation of the PageRank for Addgene took 0.020156383514404297s
Interlinking | Calculation of Degree of Connection for Addgene took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.337860107421875e-05s
Believability | Calculation of trust value for Addgene took 5.245208740234375e-06s
INFO | --- Analysis for addgene took 15.5348379611969s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.291534423828125e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.27121853828430176s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.01993846893310547s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 9.608268737792969e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 5.245208740234375e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 4.6480677127838135s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.5708889961242676s
Availability | VoID file availability check for AEMET metereological dataset took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.28409862518310547s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020109176635742188s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 5.9604644775390625e-06s
INFO | --- Analysis for aemet took 5.150399684906006s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.124641418457031e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.25816798210144043s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 2.8133392333984375e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.8858702182769775s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.03196382522583008s
Availability | VoID file availability check for AgriNepalData took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.26381373405456543s
Reputation | Calculation of the PageRank for AgriNepalData took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.866455078125e-05s
Believability | Calculation of trust value for AgriNepalData took 6.67572021484375e-06s
INFO | --- Analysis for agrinepaldata took 2.438230037689209s
Availability | SPARQL endpoint availability check for AGRIS took 262.07273387908936s
Availability | VoID file availability check for AGRIS took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for AGRIS took 0.2632880210876465s
Reputation | Calculation of the PageRank for AGRIS took 0.02084183692932129s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for AGRIS took 0.0001354217529296875s
Believability | Calculation of trust value for AGRIS took 6.67572021484375e-06s
INFO | --- Analysis for agris took 557.2117519378662s
Availability | SPARQL endpoint availability check for AGROVOC took 0.2407388687133789s
Availability | VoID file availability check for AGROVOC took 0.0005621910095214844s
Extra | Recovery of all triples for AGROVOC took 30.780055284500122s
Performance | Total latancy measurement for AGROVOC took 0.41356492042541504s
Amount of data | Number of triples check for AGROVOC took 11.865750551223755s
Interoperability | New terms check for AGROVOC took 3.2707695960998535s
Versatility | Languages check for AGROVOC took 0.19432735443115234s
Interpretability | Number of blank nodes check for AGROVOC took 0.1932375431060791s
Interpretability | RDF structures check for AGROVOC took 0.19307661056518555s
Versatility | Serialization formats check for AGROVOC took 0.18303728103637695s
Availability | RDF dump link check for AGROVOC took 0.18186426162719727s
License | MR license check for AGROVOC took 0.17028427124023438s
License | HR license check for AGROVOC took 0.18820762634277344s
Amount of data | Number of property check for AGROVOC took 0.1725170612335205s
Understandability | Number of label check for AGROVOC took 0.1747138500213623s
Understandability | URI regex check for AGROVOC took 0.3868405818939209s
Understandability | Vocabs check for AGROVOC took 0.19414758682250977s
Verifiability | Authors check for AGROVOC took 0.18388032913208008s
Verifiability | Publishers check for AGROVOC took 0.1826169490814209s
Amount of data | Check the number of entities for AGROVOC took 0.00010919570922851562s
Verifiability | Contribs. check for AGROVOC took 0.18572473526000977s
Interlinking | sameAs chians check for AGROVOC took 0.1831684112548828s
Interlinking | skos check for AGROVOC took 0.18149638175964355s
Interlinking | skos check for AGROVOC took 0.1836855411529541s
Timeliness | dataset update frequency check for AGROVOC took 0.1824963092803955s
Currency | Creation date check for AGROVOC took 0.36453914642333984s
Currency | Modification date check for AGROVOC took 0.3507721424102783s
Rep.Conc. | URIs length for AGROVOC took 0.38907790184020996s
Interoperability | New vocabularies check for AGROVOC took 4.76837158203125e-07s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.1827704906463623s
Consistency | Disjoint class check for AGROVOC took 0.18857026100158691s
Consistency | Check Ontology hijacking for AGROVOC took 0.18218779563903809s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 1.5347392559051514s
Conciseness | Check Extensional conciseness for AGROVOC took 0.00014543533325195312s
Security | Sign check for AGROVOC took 0.1700589656829834s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.7627980709075928s
Reputation | Calculation of the PageRank for AGROVOC took 0.020338058471679688s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011086463928222656s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 4.76837158203125e-07s
Believability | Calculation of trust value for AGROVOC took 6.67572021484375e-06s
INFO | --- Analysis for agrovoc took 64.6512041091919s
Availability | SPARQL endpoint availability check for AGROVOC took 4.982948303222656e-05s
Availability | VoID file availability check for AGROVOC took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.27251768112182617s
Reputation | Calculation of the PageRank for AGROVOC took 0.02001810073852539s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 5.7220458984375e-05s
Believability | Calculation of trust value for AGROVOC took 1.0013580322265625e-05s
INFO | --- Analysis for agrovoc-skos took 3.2577250003814697s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 0.9526872634887695s
Availability | VoID file availability check for Analytics India Magazine took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.2543323040008545s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.028161287307739258s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0010597705841064453s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.314018249511719e-05s
Believability | Calculation of trust value for Analytics India Magazine took 1.1205673217773438e-05s
INFO | --- Analysis for AIM took 5.094996929168701s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.696846008300781e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.6691696643829346s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020012617111206055s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 2.9802322387695312e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.2636184692382812e-05s
INFO | --- Analysis for AISHE took 3.1819355487823486s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.1961669921875e-05s
Availability | VoID file availability check for  equipment ontology took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.2588629722595215s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020189285278320312s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for  equipment ontology took 5.245208740234375e-06s
INFO | --- Analysis for akash took 2.325338363647461s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.124641418457031e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.2908060550689697s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020028352737426758s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.8371810913085938e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 5.7220458984375e-06s
INFO | --- Analysis for aksworg took 2.9465408325195312s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.124641418457031e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.269362211227417s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02010202407836914s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.956390380859375e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.0251998901367188e-05s
INFO | --- Analysis for alchemyapi took 2.884269952774048s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 8.702278137207031e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.26452040672302246s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020138025283813477s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.0279159545898438e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 1.0251998901367188e-05s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.826505661010742s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.295929193496704s
Availability | VoID file availability check for aliada-scanbit-net took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.237595796585083s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02010941505432129s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00010895729064941406s
Believability | Calculation of trust value for aliada-scanbit-net took 5.4836273193359375e-06s
INFO | --- Analysis for aliada-scanbit-net took 4.256635904312134s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.076957702636719e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.2584550380706787s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02005791664123535s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.9325485229492188e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 1.0967254638671875e-05s
INFO | --- Analysis for allen-brain-atlas took 2.883103847503662s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.4856922626495361s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006275177001953125s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 551.4239187240601s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.7120907306671143s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.5358967781066895s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.6058363914489746s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.1041612625122s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 4.090769052505493s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8965532779693604s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.9075577259063721s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.8920478820800781s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.6472160816192627s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.5786628723144531s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 33.23861527442932s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5919308662414551s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 0.6861307621002197s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1064081192016602s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.5768897533416748s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.5822737216949463s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5855216979980469s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 11.566832065582275s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 7.271766662597656e-05s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5484604835510254s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.5596973896026611s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6217672824859619s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.6332695484161377s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6838736534118652s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.2887084484100342s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1152637004852295s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 204.40395617485046s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5617485046386719s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.605597734451294s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.5793638229370117s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 186.05638098716736s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.172637939453125s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.6282522678375244s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.5838632583618164s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 11.075688600540161s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.857491254806519s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 130.91961216926575s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.4097344875335693s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 11.900620698928833s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.752790689468384s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8517649173736572s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5844948291778564s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 13443.049709796906s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.6510839462280273s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.021557092666625977s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 7.772445678710938e-05s
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 15018.52284169197s
Availability | SPARQL endpoint availability check for Alojamientos took 4.172325134277344e-05s
Availability | VoID file availability check for Alojamientos took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.2393960952758789s
Reputation | Calculation of the PageRank for Alojamientos took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007829666137695312s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.147125244140625e-05s
Believability | Calculation of trust value for Alojamientos took 1.2874603271484375e-05s
INFO | --- Analysis for alojamientos-zaragoza took 2.8483352661132812s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.3831338882446289s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2542099952697754s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020177602767944336s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.7670135498046875e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 6.67572021484375e-06s
INFO | --- Analysis for alpino-rdf took 4.041837930679321s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.315376281738281e-05s
Availability | VoID file availability check for AAT-atawil took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2632472515106201s
Reputation | Calculation of the PageRank for AAT-atawil took 0.02041149139404297s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.0517578125e-05s
Believability | Calculation of trust value for AAT-atawil took 7.3909759521484375e-06s
INFO | --- Analysis for Altawil took 2.807408332824707s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.506111145019531e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.25020718574523926s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020415782928466797s
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.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.0279159545898438e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.1920928955078125e-05s
INFO | --- Analysis for am-collections-online took 2.8584814071655273s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.792213439941406e-05s
Availability | VoID file availability check for Amer Nejma took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.24010801315307617s
Reputation | Calculation of the PageRank for Amer Nejma took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 2.9802322387695312e-05s
Believability | Calculation of trust value for Amer Nejma took 5.9604644775390625e-06s
INFO | --- Analysis for Amer_Nejma took 2.3438823223114014s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.26356077194213867s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020270109176635742s
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.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for amon took 2.860213041305542s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.6973767280578613s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.24961113929748535s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020307064056396484s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.107589721679688e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 5.9604644775390625e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.730769157409668s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.0531158447265625e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.250307559967041s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020184993743896484s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.266334533691406e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 9.5367431640625e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.808868169784546s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.1484832763671875e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.26027917861938477s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.0517578125e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.4373016357421875e-06s
INFO | --- Analysis for animal-diversity-web took 2.931309700012207s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.3392181396484375e-05s
Availability | VoID file availability check for Anime Dataset took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.23954558372497559s
Reputation | Calculation of the PageRank for Anime Dataset took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.147125244140625e-05s
Believability | Calculation of trust value for Anime Dataset took 1.2874603271484375e-05s
INFO | --- Analysis for Anime took 3.493441104888916s
Availability | SPARQL endpoint availability check for ANNO took 4.315376281738281e-05s
Availability | VoID file availability check for ANNO took 0.0006692409515380859s
Completeness | Calculation of interlinking completeness for ANNO took 0.26798582077026367s
Reputation | Calculation of the PageRank for ANNO took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.528594970703125e-05s
Believability | Calculation of trust value for ANNO took 7.62939453125e-06s
INFO | --- Analysis for anno took 8.479299306869507s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.5299530029296875e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2425553798675537s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.486343383789062e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 5.7220458984375e-06s
INFO | --- Analysis for AntiqueCarsCollection took 2.8028430938720703s
Availability | SPARQL endpoint availability check for apache took 4.291534423828125e-05s
Availability | VoID file availability check for apache took 0.0007576942443847656s
Completeness | Calculation of interlinking completeness for apache took 0.2688882350921631s
Reputation | Calculation of the PageRank for apache took 0.02022385597229004s
Interlinking | Calculation of Degree of Connection for apache took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for apache took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for apache took 5.269050598144531e-05s
Believability | Calculation of trust value for apache took 6.67572021484375e-06s
INFO | --- Analysis for apache took 3.1006298065185547s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2711906433105469s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.8160552978515625e-05s
Believability | Calculation of trust value for Apertium RDF took 5.4836273193359375e-06s
INFO | --- Analysis for apertium-rdf took 4.717938661575317s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2484903335571289s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.567322015762329s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.2592587471008301s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02026844024658203s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.597918272018433s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.279451847076416s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02012157440185547s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.0531158447265625e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.660399436950684s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 5.650520324707031e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.25202512741088867s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.00543212890625e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.677980422973633s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 8.988380432128906e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.25628089904785156s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02167987823486328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 3.910064697265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0010654926300048828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 5.173683166503906e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.522028923034668s
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.0005376338958740234s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.28324270248413086s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.020213842391967773s
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.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 5.611428260803223s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0005993843078613281s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2555577754974365s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-eo-es took 5.558303356170654s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.8160552978515625e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0005936622619628906s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.27175188064575195s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 8.58306884765625e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.552706241607666s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2937164306640625s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020168066024780273s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007255077362060547s
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.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.582544565200806s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.305462121963501s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.600407123565674s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.315376281738281e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.24846720695495605s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007326602935791016s
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 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.871088981628418s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.2690412998199463s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.567708492279053s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.260922908782959s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.485320806503296s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2469346523284912s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020164966583251953s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.124641418457031e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.566843509674072s
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.0005173683166503906s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2777533531188965s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02010369300842285s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.029273986816406e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 8.344650268554688e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.94244384765625s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2674407958984375s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0010120868682861328s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.125999450683594e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 5.540881872177124s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.2718782424926758s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02019333839416504s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.473994493484497s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.280242919921875s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0008637905120849609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.76837158203125e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.559673070907593s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2770378589630127s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.2438507080078125e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 5.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.589246988296509s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.673004150390625e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2823371887207031s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.537147045135498s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.482269287109375e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.25333166122436523s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.021178483963012695s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.585927963256836s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2696876525878906s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.0201566219329834s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.282193422317505s
Availability | SPARQL endpoint availability check for AragoDBPedia took 2.068798065185547s
Availability | VoID file availability check for AragoDBPedia took 0.0006554126739501953s
Extra | Recovery of all triples for AragoDBPedia took 3.6029367446899414s
Performance | Total latancy measurement for AragoDBPedia took 1.9240996837615967s
Amount of data | Number of triples check for AragoDBPedia took 0.9102635383605957s
Interoperability | New terms check for AragoDBPedia took 2.1175880432128906s
Versatility | Languages check for AragoDBPedia took 60.531306982040405s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.572158098220825s
Security | Check HTTPS for AragoDBPedia took 0.31792736053466797s
Interpretability | RDF structures check for AragoDBPedia took 0.7826724052429199s
Versatility | Serialization formats check for AragoDBPedia took 1.180793285369873s
Availability | RDF dump link check for AragoDBPedia took 0.42566752433776855s
License | MR license check for AragoDBPedia took 0.8634259700775146s
License | HR license check for AragoDBPedia took 8.13398003578186s
Amount of data | Number of property check for AragoDBPedia took 0.480363130569458s
Understandability | Number of label check for AragoDBPedia took 0.7552332878112793s
Understandability | URI regex check for AragoDBPedia took 0.9733939170837402s
Understandability | Vocabs check for AragoDBPedia took 0.5160617828369141s
Verifiability | Authors check for AragoDBPedia took 0.6641905307769775s
Verifiability | Publishers check for AragoDBPedia took 0.5106382369995117s
Performance | Throughput check for AragoDBPedia took 11.891327857971191s
Amount of data | Check the number of entities for AragoDBPedia took 7.534027099609375e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.5604794025421143s
Interlinking | sameAs chians check for AragoDBPedia took 0.4721856117248535s
Interlinking | skos check for AragoDBPedia took 0.8335895538330078s
Interlinking | skos check for AragoDBPedia took 0.386568546295166s
Timeliness | dataset update frequency check for AragoDBPedia took 1.4741997718811035s
Currency | Creation date check for AragoDBPedia took 1.8675932884216309s
Currency | Modification date check for AragoDBPedia took 0.9239346981048584s
Rep.Conc. | URIs length for AragoDBPedia took 5.889069080352783s
Interoperability | New vocabularies check for AragoDBPedia took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.42645263671875s
Accuracy | Check Functional Property for AragoDBPedia took 0.6408030986785889s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.5547783374786377s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.4281535148620605s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030730724334716797s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.02754831314086914s
Consistency | Disjoint class check for AragoDBPedia took 0.6861674785614014s
Consistency | Check Misplaced properties for AragoDBPedia took 4.664076805114746s
Consistency | Misplaced classes for AragoDBPedia took 0.6579692363739014s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.774674415588379s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.304272174835205s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.701327085494995s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.031137943267822266s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.6669509410858154s
Security | Sign check for AragoDBPedia took 0.8325564861297607s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3378.869664669037s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 1.6114425659179688s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for AragoDBPedia took 5.4836273193359375e-06s
INFO | --- Analysis for aragodbpedia took 14996.398718833923s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.418295860290527s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.28509044647216797s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.02074408531188965s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.696846008300781e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for archiveshub-linkeddata took 84.3707959651947s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.1484832763671875e-05s
Availability | VoID file availability check for Archivi ISMA took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.7012310028076172s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020174264907836914s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 3.6716461181640625e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 2.9087066650390625e-05s
Believability | Calculation of trust value for Archivi ISMA took 6.4373016357421875e-06s
INFO | --- Analysis for archivio-isma took 5.07515287399292s
Availability | SPARQL endpoint availability check for ARIADNE took 4.291534423828125e-05s
Availability | VoID file availability check for ARIADNE took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2566239833831787s
Reputation | Calculation of the PageRank for ARIADNE took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.1948089599609375e-05s
Believability | Calculation of trust value for ARIADNE took 7.867813110351562e-06s
INFO | --- Analysis for ariadne took 3.289254665374756s
Availability | SPARQL endpoint availability check for Aristotle University took 4.172325134277344e-05s
Availability | VoID file availability check for Aristotle University took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.6854524612426758s
Reputation | Calculation of the PageRank for Aristotle University took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for Aristotle University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 2.6941299438476562e-05s
Believability | Calculation of trust value for Aristotle University took 6.67572021484375e-06s
INFO | --- Analysis for aristotle-university took 3.3338687419891357s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.900948524475098s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2608213424682617s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.021071434020996094s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.838539123535156e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.152557373046875e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.265094995498657s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.124641418457031e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.26740527153015137s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 6.4373016357421875e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.8173139095306396s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.9330015182495117s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.28879594802856445s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.743171691894531e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 5.0067901611328125e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 17.411046981811523s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 5.793571472167969e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006694793701171875s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2562229633331299s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020152568817138672s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.000102996826171875s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 9.999321222305298s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.172325134277344e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.2778193950653076s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.1205673217773438e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 6.198883056640625e-06s
INFO | --- Analysis for Arthron took 2.329685688018799s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.3392181396484375e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2556009292602539s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.846687316894531e-05s
Believability | Calculation of trust value for Arthroscopy community took 8.106231689453125e-06s
INFO | --- Analysis for arthroscopy took 14.259178638458252s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.7152738571166992s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0006132125854492188s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 0.06982183456420898s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 0.08310604095458984s
Versatility | Languages check for Wikidata entry for Art × Science International took 0.09180307388305664s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 0.08068561553955078s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.0697622299194336s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.09411001205444336s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.08453035354614258s
License | MR license check for Wikidata entry for Art × Science International took 0.09489202499389648s
License | HR license check for Wikidata entry for Art × Science International took 0.08336687088012695s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.08087944984436035s
Understandability | Number of label check for Wikidata entry for Art × Science International took 0.08345222473144531s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.16471314430236816s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.08293771743774414s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.08267569541931152s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.07198739051818848s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 0.00013399124145507812s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.07245445251464844s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 0.07187128067016602s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.0814058780670166s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.0819861888885498s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.07232475280761719s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.16734027862548828s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.17490243911743164s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 0.16515374183654785s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.09235119819641113s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.08349895477294922s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 0.09384036064147949s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 1.4362127780914307s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 0.00014400482177734375s
Security | Sign check for Wikidata entry for Art × Science International took 0.06908965110778809s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.24553513526916504s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 4.76837158203125e-07s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 6.67572021484375e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 20.301140785217285s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 39.02277898788452s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.2605452537536621s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.130073547363281e-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 79.94047570228577s
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 0.03202533721923828s
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.0006899833679199219s
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.27088141441345215s
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.020293235778808594s
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 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0007283687591552734s
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.414817810058594e-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 79.969970703125s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.028388261795043945s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.25653743743896484s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02016425132751465s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.179115295410156e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 79.9722192287445s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 0.03343796730041504s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2858467102050781s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.172325134277344e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-CRB took 80.0013358592987s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.029572725296020508s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0008020401000976562s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2528493404388428s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.107589721679688e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 80.10719847679138s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 0.03098893165588379s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2694981098175049s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.62396240234375e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-DQOT took 80.38535857200623s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.037642717361450195s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2663393020629883s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.02028512954711914s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.822845458984375e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 79.93407154083252s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 39.02196478843689s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006887912750244141s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.3175992965698242s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020599365234375s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.748603820800781e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 139.91497159004211s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 39.02695560455322s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.27805233001708984s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.507469177246094e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.9604644775390625e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 79.96724081039429s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.03007054328918457s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.6835086345672607s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.221366882324219e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 80.78160452842712s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 2.240140676498413s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.6815016269683838s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.698204040527344e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 82.79470324516296s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 39.02090334892273s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.7105841636657715s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.605552673339844e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 81.75900316238403s
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 39.02470588684082s
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.0004792213439941406s
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.24059581756591797s
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.020363330841064453s
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 8.58306884765625e-06s
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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 8.344650268554688e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 80.846519947052s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 0.0287020206451416s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.24827885627746582s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.315376281738281e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 8.106231689453125e-06s
INFO | --- Analysis for ASCDC_-_DNB took 40.881513833999634s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.1961669921875e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2589447498321533s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02016472816467285s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.29425048828125e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.1920928955078125e-05s
INFO | --- Analysis for asit took 7.613625764846802s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.220008850097656e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.2442011833190918s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02079296112060547s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.695487976074219e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 6.9141387939453125e-06s
INFO | --- Analysis for asjp took 4.535425901412964s
Availability | SPARQL endpoint availability check for ASN:US took 0.10626792907714844s
Availability | VoID file availability check for ASN:US took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2539384365081787s
Reputation | Calculation of the PageRank for ASN:US took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.389617919921875e-05s
Believability | Calculation of trust value for ASN:US took 5.4836273193359375e-06s
INFO | --- Analysis for asn-us took 6.245172739028931s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.3392181396484375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.262800931930542s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.9325485229492188e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 4.76837158203125e-06s
INFO | --- Analysis for aspire-mmu took 4.456241130828857s
Availability | SPARQL endpoint availability check for associations took 4.315376281738281e-05s
Availability | VoID file availability check for associations took 0.0006990432739257812s
Completeness | Calculation of interlinking completeness for associations took 0.28435397148132324s
Reputation | Calculation of the PageRank for associations took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for associations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for associations took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for associations took 6.67572021484375e-05s
Believability | Calculation of trust value for associations took 6.4373016357421875e-06s
INFO | --- Analysis for associations took 7.301796913146973s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.3392181396484375e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2571101188659668s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.218650817871094e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 6.198883056640625e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.860168933868408s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 5.888938903808594e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.24385809898376465s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.630752563476562e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.867813110351562e-06s
INFO | --- Analysis for athelia-rfid took 4.041130781173706s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.4345855712890625e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0003476142883300781s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2581043243408203s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 3.170967102050781e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 6.198883056640625e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.886305570602417s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 1.5601916313171387s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006806850433349609s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.24478888511657715s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.792213439941406e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for AugustiniConfessiones took 5.761992931365967s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6592917442321777s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2627584934234619s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.726119995117188e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 6.67572021484375e-06s
INFO | --- Analysis for austrian_ski_racers took 3.840074062347412s
Availability | SPARQL endpoint availability check for AVsOnto took 4.124641418457031e-05s
Availability | VoID file availability check for AVsOnto took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.26486968994140625s
Reputation | Calculation of the PageRank for AVsOnto took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for AVsOnto took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007810592651367188s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.075599670410156e-05s
Believability | Calculation of trust value for AVsOnto took 5.7220458984375e-06s
INFO | --- Analysis for AVsOnto took 3.2908897399902344s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3008542060852051s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0006010532379150391s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 186.85119771957397s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5359737873077393s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0882978439331s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 191.14225387573242s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0997304916382s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0940296649933s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2459259033203125s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21050429344177246s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.19263482093811035s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10493850708007812s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 51.2233669757843s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0144281387329s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.17065978050231934s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 210.64077305793762s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2544887065887451s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11516785621643066s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11008524894714355s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11239194869995117s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.495042324066162s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.510185241699219e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09885215759277344s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.055312871933s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2970881462097168s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11922955513000488s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14779973030090332s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23661279678344727s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.25566911697387695s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 636.2087545394897s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15465784072875977s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 31.119741678237915s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.255831480026245s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.79088282585144s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15890836715698242s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.1319742202759s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 152.84403347969055s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.2868056297302246s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.5299813747406s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.796365976333618s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.18404030799865723s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.359060764312744s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.7166252136230469s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021374225616455078s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.390975952148438e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1457672119140625e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.0067901611328125e-06s
INFO | --- Analysis for b3kat took 4237.446293354034s
Availability | SPARQL endpoint availability check for BabelNet took 0.5512478351593018s
Availability | VoID file availability check for BabelNet took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for BabelNet took 0.26989030838012695s
Reputation | Calculation of the PageRank for BabelNet took 0.022025108337402344s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0009417533874511719s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001842975616455078s
Believability | Calculation of trust value for BabelNet took 1.0013580322265625e-05s
INFO | --- Analysis for babelnet took 5.304576635360718s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.4345855712890625e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.7398231029510498s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020333528518676758s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.147125244140625e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.2159347534179688e-05s
INFO | --- Analysis for Bacevicius.lt took 3.685587167739868s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.4643375873565674s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.25347113609313965s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020617008209228516s
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.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.38690185546875e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 5.9604644775390625e-06s
INFO | --- Analysis for bag took 4.317652225494385s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 1.5552842617034912s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2806859016418457s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.1948089599609375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 5.7220458984375e-06s
INFO | --- Analysis for baixue took 4.485544204711914s
Availability | SPARQL endpoint availability check for baixue composer took 5.5789947509765625e-05s
Availability | VoID file availability check for baixue composer took 0.0003402233123779297s
Completeness | Calculation of interlinking completeness for baixue composer took 0.27661943435668945s
Reputation | Calculation of the PageRank for baixue composer took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for baixue composer took 4.0531158447265625e-05s
Believability | Calculation of trust value for baixue composer took 7.152557373046875e-06s
INFO | --- Analysis for baixue_composer took 2.9481635093688965s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.6253204345703125e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2687265872955322s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.1948089599609375e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.4373016357421875e-06s
INFO | --- Analysis for baixue_imagery took 2.6218433380126953s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.841255187988281e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.27011561393737793s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02064657211303711s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.2901763916015625e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.4373016357421875e-06s
INFO | --- Analysis for baixue_imagery1 took 3.5385777950286865s
Availability | SPARQL endpoint availability check for BAMS took 4.2438507080078125e-05s
Availability | VoID file availability check for BAMS took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for BAMS took 0.2672712802886963s
Reputation | Calculation of the PageRank for BAMS took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for BAMS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.337860107421875e-05s
Believability | Calculation of trust value for BAMS took 1.0013580322265625e-05s
INFO | --- Analysis for bams took 2.8952746391296387s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 5.698204040527344e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.29169631004333496s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.02028346061706543s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.00090789794921875s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 8.344650268554688e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.940863609313965s
Availability | SPARQL endpoint availability check for BBC Music took 0.3396470546722412s
Availability | VoID file availability check for BBC Music took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for BBC Music took 0.269665002822876s
Reputation | Calculation of the PageRank for BBC Music took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for BBC Music took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BBC Music took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.0001239776611328125s
Believability | Calculation of trust value for BBC Music took 5.9604644775390625e-06s
INFO | --- Analysis for bbc-music took 3.2957541942596436s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.26638007164001465s
Availability | VoID file availability check for BBC Programmes took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.24695467948913574s
Reputation | Calculation of the PageRank for BBC Programmes took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010132789611816406s
Believability | Calculation of trust value for BBC Programmes took 1.1205673217773438e-05s
INFO | --- Analysis for bbc-programmes took 11.2947678565979s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.4014546871185303s
Availability | VoID file availability check for BBC Wildlife Finder took 0.00042510032653808594s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.24425816535949707s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010180473327636719s
Believability | Calculation of trust value for BBC Wildlife Finder took 5.4836273193359375e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.720731973648071s
Availability | SPARQL endpoint availability check for BBOP took 4.1961669921875e-05s
Availability | VoID file availability check for BBOP took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for BBOP took 0.283306360244751s
Reputation | Calculation of the PageRank for BBOP took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for BBOP took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.123283386230469e-05s
Believability | Calculation of trust value for BBOP took 7.152557373046875e-06s
INFO | --- Analysis for bbop took 2.8525967597961426s
Availability | SPARQL endpoint availability check for BBOP took 0.00014448165893554688s
Availability | VoID file availability check for BBOP took 0.0008172988891601562s
Completeness | Calculation of interlinking completeness for BBOP took 0.25394105911254883s
Reputation | Calculation of the PageRank for BBOP took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.147125244140625e-05s
Believability | Calculation of trust value for BBOP took 1.0251998901367188e-05s
INFO | --- Analysis for bbop-selected took 19.96828532218933s
Availability | SPARQL endpoint availability check for Bdgp took 1.6774303913116455s
Availability | VoID file availability check for Bdgp took 0.0005853176116943359s
Completeness | Calculation of interlinking completeness for Bdgp took 0.27072691917419434s
Reputation | Calculation of the PageRank for Bdgp took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.0517578125e-05s
Believability | Calculation of trust value for Bdgp took 8.58306884765625e-06s
INFO | --- Analysis for bdgp took 8.500908851623535s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.267692565917969e-05s
Availability | VoID file availability check for Bendev Junior took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.26483750343322754s
Reputation | Calculation of the PageRank for Bendev Junior took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bendev Junior took 7.152557373046875e-06s
INFO | --- Analysis for bendevoficial took 5.401217222213745s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.1366212368011475s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2557036876678467s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020193099975585938s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.985664367675781e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.245208740234375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 11.339874505996704s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 3.981590270996094e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.270937442779541s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.7894973754882812e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 7.3909759521484375e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.8899145126342773s
Availability | SPARQL endpoint availability check for berlios took 4.3392181396484375e-05s
Availability | VoID file availability check for berlios took 0.0003960132598876953s
Completeness | Calculation of interlinking completeness for berlios took 0.2784886360168457s
Reputation | Calculation of the PageRank for berlios took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for berlios took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for berlios took 8.678436279296875e-05s
Believability | Calculation of trust value for berlios took 7.3909759521484375e-06s
INFO | --- Analysis for berlios took 2.5725595951080322s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.172325134277344e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.30615973472595215s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020375728607177734s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.437301635742188e-05s
Believability | Calculation of trust value for Between Our Worlds took 7.62939453125e-06s
INFO | --- Analysis for betweenourworlds took 9.357628345489502s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.5329782962799072s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.26386070251464844s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.654594421386719e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for bfs-linked-data took 3.0392966270446777s
Availability | SPARQL endpoint availability check for BibBase took 0.06658935546875s
Availability | VoID file availability check for BibBase took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for BibBase took 0.26308655738830566s
Reputation | Calculation of the PageRank for BibBase took 0.02027416229248047s
Interlinking | Calculation of Degree of Connection for BibBase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.274482727050781e-05s
Believability | Calculation of trust value for BibBase took 6.198883056640625e-06s
INFO | --- Analysis for bibbase took 2.4937050342559814s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.1961669921875e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.29413557052612305s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.441375732421875e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 6.4373016357421875e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 5.659224987030029s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.440017700195312e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.26965880393981934s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.5367431640625e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 6.4373016357421875e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.599165439605713s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.124641418457031e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.26564788818359375s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 2.86102294921875e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 5.7220458984375e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.854377508163452s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.220008850097656e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.2695126533508301s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020992279052734375s
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.00070953369140625s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.361701965332031e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 6.4373016357421875e-06s
INFO | --- Analysis for BibSonomy took 9.003067255020142s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.1484832763671875e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2506842613220215s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.02013993263244629s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.956390380859375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 5.7220458984375e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 4.626191139221191s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.24830031394958496s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020447492599487305s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.62939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.5250842571258545s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.363059997558594e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.249894380569458s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.876161813735962s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.8869497776031494s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005838871002197266s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 37.59292960166931s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.522019624710083s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 44.93734574317932s
Interoperability | New terms check for Bio2RDF::Affymetrix took 43.29277324676514s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.122599601745605s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.13236451148986816s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 0.8485260009765625s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.2591867446899414s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 6.2441840171813965s
License | MR license check for Bio2RDF::Affymetrix took 0.33583831787109375s
License | HR license check for Bio2RDF::Affymetrix took 60.10289168357849s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.15314078330993652s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.786339044570923s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.4309194087982178s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.14156222343444824s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.20217013359069824s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.13390660285949707s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.719051599502563s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 72.12005472183228s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.590944766998291s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.22530579566955566s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.7507166862487793s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.1949446201324463s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.12686872482299805s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.26950860023498535s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2391195297241211s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 120.2244770526886s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.31830835342407227s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15021276473999023s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.12117385864257812s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 18.978230953216553s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.9075884819030762s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6740105152130127s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.3699169158935547s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 70.70756077766418s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.2772746086120605s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 11.875103950500488s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.3344295024871826s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.36932635307312s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.6878459453582764s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.2892313003540039s
Security | Sign check for Bio2RDF::Affymetrix took 0.11288070678710938s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 11.091743230819702s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.8758845329284668s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020143985748291016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.34600830078125e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-affymetrix took 1079.3196930885315s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.4883887767791748s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0003952980041503906s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 34.4847149848938s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.2426822185516357s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.3029248714447s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.756309270858765s
Versatility | Languages check for Bio2RDF::Biomodels took 60.25495982170105s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.266021728515625s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.14763736724853516s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.9066982269287109s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.368419885635376s
Availability | RDF dump link check for Bio2RDF::Biomodels took 6.290482997894287s
License | MR license check for Bio2RDF::Biomodels took 0.5665435791015625s
License | HR license check for Bio2RDF::Biomodels took 60.251012086868286s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.28682374954223633s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.379248857498169s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.6140425205230713s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2638833522796631s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.2962017059326172s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.261122465133667s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 77.0801568031311s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.9478750228881836s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.36897850036621094s
Interlinking | skos check for Bio2RDF::Biomodels took 1.0691766738891602s
Interlinking | skos check for Bio2RDF::Biomodels took 0.354719877243042s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2784595489501953s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5380728244781494s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5176398754119873s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 121.67887377738953s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.43281102180480957s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.2889244556427002s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.30207133293151855s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 18.375722885131836s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.9029154777526855s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6610796451568604s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.43208885192871094s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 70.87438535690308s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4425108432769775s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 11.703131437301636s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.3596479892730713s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.58573818206787s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.7015137672424316s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 0.43419885635375977s
Security | Sign check for Bio2RDF::Biomodels took 0.2824435234069824s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 11.334643363952637s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.9488534927368164s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00010895729064941406s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-biomodels took 1063.6512022018433s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.705622673034668s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 4.6666319370269775s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.4648630619049072s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0006489753723144531s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 38.52878665924072s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.236243724822998s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 43.6091947555542s
Interoperability | New terms check for Bio2RDF::Bioportal took 41.705466508865356s
Versatility | Languages check for Bio2RDF::Bioportal took 60.2701849937439s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2690854072570801s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.14889144897460938s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.9389157295227051s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.36073875427246094s
Availability | RDF dump link check for Bio2RDF::Bioportal took 6.3708579540252686s
License | MR license check for Bio2RDF::Bioportal took 0.564424991607666s
License | HR license check for Bio2RDF::Bioportal took 60.259936809539795s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2764284610748291s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.983855485916138s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.576305627822876s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.2591705322265625s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.2926671504974365s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.25275373458862305s
Performance | Throughput check for Bio2RDF::Bioportal took 10.24426531791687s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 73.22310972213745s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.29248547554016113s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3856825828552246s
Interlinking | skos check for Bio2RDF::Bioportal took 1.1358871459960938s
Interlinking | skos check for Bio2RDF::Bioportal took 0.40948057174682617s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.28168201446533203s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5422368049621582s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5319247245788574s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 120.56300377845764s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.4709954261779785s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.304431676864624s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.29973340034484863s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 19.51634120941162s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8904335498809814s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6552276611328125s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.5847067832946777s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 70.83528661727905s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.5447797775268555s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 11.788896560668945s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.3310530185699463s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.59937143325806s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7124981880187988s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.46058082580566406s
Security | Sign check for Bio2RDF::Bioportal took 0.29744410514831543s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 11.874154806137085s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.8887345790863037s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0004162788391113281s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1076.365103006363s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.13622474670410156s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.25974273681640625s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.316734313964844e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-chembl took 17.117565870285034s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.4752514362335205s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0005657672882080078s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 35.45259189605713s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.2655746936798096s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 44.24498128890991s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 41.7688775062561s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.241435050964355s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2664031982421875s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.15667462348937988s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.7942495346069336s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.34928464889526367s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 6.331599235534668s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5483064651489258s
License | HR license check for Bio2RDF::Clinicaltrials took 60.25008583068848s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.26202392578125s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.102074384689331s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.6044206619262695s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.27153706550598145s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2900962829589844s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.2623143196105957s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.582682132720947s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 75.25598287582397s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 0.5619151592254639s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.4150979518890381s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 1.0676541328430176s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.3785381317138672s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.28789472579956055s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5417983531951904s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5262477397918701s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 118.9541711807251s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.4118056297302246s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.29352307319641113s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2727816104888916s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 18.75069284439087s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8974833488464355s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6644761562347412s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.5155305862426758s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 70.56429123878479s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.429891347885132s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 11.90048360824585s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.3023920059204102s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.55319285392761s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.6974523067474365s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.47696876525878906s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.27799201011657715s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 11.16258430480957s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 1.4500985145568848s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02012491226196289s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 5.340576171875e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1071.5209333896637s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.4795370101928711s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0006833076477050781s
Extra | Recovery of all triples for Bio2RDF::Ctd took 33.87559127807617s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.2593178749084473s
Amount of data | Number of triples check for Bio2RDF::Ctd took 44.271605491638184s
Interoperability | New terms check for Bio2RDF::Ctd took 40.802979469299316s
Versatility | Languages check for Bio2RDF::Ctd took 60.22986936569214s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.2838935852050781s
Security | Check HTTPS for Bio2RDF::Ctd took 0.14490556716918945s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.8536770343780518s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3367457389831543s
Availability | RDF dump link check for Bio2RDF::Ctd took 6.290303945541382s
License | MR license check for Bio2RDF::Ctd took 0.5292797088623047s
License | HR license check for Bio2RDF::Ctd took 60.2512583732605s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.2582366466522217s
Understandability | Number of label check for Bio2RDF::Ctd took 10.337307691574097s
Understandability | URI regex check for Bio2RDF::Ctd took 0.6128411293029785s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.2710230350494385s
Verifiability | Authors check for Bio2RDF::Ctd took 0.27724432945251465s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.2556757926940918s
Performance | Throughput check for Bio2RDF::Ctd took 11.02707815170288s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 72.45923137664795s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.5791254043579102s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3980855941772461s
Interlinking | skos check for Bio2RDF::Ctd took 1.060682773590088s
Interlinking | skos check for Bio2RDF::Ctd took 0.3314669132232666s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.26814818382263184s
Currency | Creation date check for Bio2RDF::Ctd took 0.5488693714141846s
Currency | Modification date check for Bio2RDF::Ctd took 0.5110297203063965s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 122.05621552467346s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.4611542224884033s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.27985453605651855s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.28316426277160645s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 18.04990863800049s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8922171592712402s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6755905151367188s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.4454796314239502s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 70.77872967720032s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.464149236679077s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 12.166833639144897s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3593719005584717s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.558005571365356s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.6957204341888428s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.435211181640625s
Security | Sign check for Bio2RDF::Ctd took 0.26751017570495605s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.878523826599121s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.8190569877624512s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.02495718002319336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.628036499023438e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ctd took 1072.9803249835968s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.220008850097656e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.6887392997741699s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.863739013671875e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-dataset took 4.542681694030762s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.4573085308074951s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005626678466796875s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 34.239617586135864s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2969825267791748s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.166216135025024s
Interoperability | New terms check for Bio2RDF::Dbsnp took 42.38859820365906s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.23048210144043s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.27327394485473633s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.15706658363342285s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 1.1812398433685303s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.34079957008361816s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 6.332223653793335s
License | MR license check for Bio2RDF::Dbsnp took 0.5359742641448975s
License | HR license check for Bio2RDF::Dbsnp took 60.25001382827759s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.3074204921722412s
Understandability | Number of label check for Bio2RDF::Dbsnp took 9.990054845809937s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.6120061874389648s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.2721235752105713s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.29121899604797363s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.24016809463500977s
Performance | Throughput check for Bio2RDF::Dbsnp took 10.607554197311401s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 74.87942051887512s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 0.5795979499816895s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3354058265686035s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.8376269340515137s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.3604927062988281s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.2947196960449219s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5177855491638184s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5447001457214355s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 122.14167022705078s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.5041635036468506s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.27883362770080566s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.2861323356628418s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 17.744242906570435s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.905590295791626s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.666039228439331s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.40297460556030273s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 71.14162468910217s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.3900606632232666s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 11.75373911857605s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3487522602081299s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.59105920791626s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7076537609100342s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 1.4061939716339111s
Security | Sign check for Bio2RDF::Dbsnp took 0.26752328872680664s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 11.630143880844116s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.5078508853912354s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.019884824752807617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 7.033348083496094e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 1094.7967178821564s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 1.2866852283477783s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006144046783447266s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 33.72763919830322s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2605130672454834s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 43.71399521827698s
Interoperability | New terms check for Bio2RDF::Drugbank took 42.296549797058105s
Versatility | Languages check for Bio2RDF::Drugbank took 60.24060797691345s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.25713324546813965s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.1692643165588379s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.40750622749328613s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3700907230377197s
Availability | RDF dump link check for Bio2RDF::Drugbank took 6.365697383880615s
License | MR license check for Bio2RDF::Drugbank took 0.4576835632324219s
License | HR license check for Bio2RDF::Drugbank took 60.241607904434204s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.27365636825561523s
Understandability | Number of label check for Bio2RDF::Drugbank took 9.803053617477417s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.6041760444641113s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.2683405876159668s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.2615945339202881s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.281130313873291s
Performance | Throughput check for Bio2RDF::Drugbank took 10.659616470336914s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 76.94536924362183s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 2.074007272720337s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.35306668281555176s
Interlinking | skos check for Bio2RDF::Drugbank took 0.7710011005401611s
Interlinking | skos check for Bio2RDF::Drugbank took 0.33412671089172363s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2867753505706787s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5430715084075928s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5408034324645996s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 120.64197635650635s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4320952892303467s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.28005218505859375s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.2893085479736328s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 17.72113299369812s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.899632453918457s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.6609585285186768s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.4801805019378662s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 71.18624496459961s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.4126689434051514s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 11.786139011383057s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3470392227172852s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.570337533950806s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.6939618587493896s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.6013226509094238s
Security | Sign check for Bio2RDF::Drugbank took 0.29732275009155273s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 11.559238910675049s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 1.024634838104248s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00011134147644042969s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1091.5839953422546s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.48694801330566406s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0005590915679931641s
Extra | Recovery of all triples for Bio2RDF::Genage took 36.13278770446777s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.258629560470581s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.91953372955322s
Interoperability | New terms check for Bio2RDF::Genage took 41.94788312911987s
Versatility | Languages check for Bio2RDF::Genage took 60.24362325668335s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2777681350708008s
Security | Check HTTPS for Bio2RDF::Genage took 0.15999484062194824s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.6980078220367432s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.3345339298248291s
Availability | RDF dump link check for Bio2RDF::Genage took 6.318161249160767s
License | MR license check for Bio2RDF::Genage took 0.833505392074585s
License | HR license check for Bio2RDF::Genage took 60.270275592803955s
Amount of data | Number of property check for Bio2RDF::Genage took 0.30552029609680176s
Understandability | Number of label check for Bio2RDF::Genage took 10.628216981887817s
Understandability | URI regex check for Bio2RDF::Genage took 0.5945069789886475s
Understandability | Vocabs check for Bio2RDF::Genage took 0.28035807609558105s
Verifiability | Authors check for Bio2RDF::Genage took 0.29439806938171387s
Verifiability | Publishers check for Bio2RDF::Genage took 0.257976770401001s
Performance | Throughput check for Bio2RDF::Genage took 10.633261680603027s
Amount of data | Check the number of entities for Bio2RDF::Genage took 73.78069639205933s
Verifiability | Contribs. check for Bio2RDF::Genage took 2.052710771560669s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.360950231552124s
Interlinking | skos check for Bio2RDF::Genage took 0.9726667404174805s
Interlinking | skos check for Bio2RDF::Genage took 0.3676176071166992s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.28873705863952637s
Currency | Creation date check for Bio2RDF::Genage took 0.5614562034606934s
Currency | Modification date check for Bio2RDF::Genage took 0.5542035102844238s
Rep.Conc. | URIs length for Bio2RDF::Genage took 121.87000298500061s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4523203372955322s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.29646754264831543s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.27440357208251953s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 18.886070251464844s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.9039425849914551s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6651279926300049s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.44314074516296387s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 70.6551947593689s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.38440203666687s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 11.551353454589844s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.30009126663208s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.54435157775879s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7094531059265137s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.43605685234069824s
Security | Sign check for Bio2RDF::Genage took 0.28252649307250977s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 11.170396566390991s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.53299880027771s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 6.914138793945312e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genage took 1078.3871989250183s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.2608804702758789s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.841255187988281e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.430511474609375e-05s
INFO | --- Analysis for bio2rdf-genbank took 5.573786497116089s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 1.269820213317871s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0003292560577392578s
Extra | Recovery of all triples for Bio2RDF::Gendr took 36.78579139709473s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.267596960067749s
Amount of data | Number of triples check for Bio2RDF::Gendr took 45.93092131614685s
Interoperability | New terms check for Bio2RDF::Gendr took 41.6117901802063s
Versatility | Languages check for Bio2RDF::Gendr took 60.280781269073486s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.2864811420440674s
Security | Check HTTPS for Bio2RDF::Gendr took 0.16960358619689941s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.8908607959747314s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.359846830368042s
Availability | RDF dump link check for Bio2RDF::Gendr took 6.360626220703125s
License | MR license check for Bio2RDF::Gendr took 0.5314953327178955s
License | HR license check for Bio2RDF::Gendr took 60.25862240791321s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2676856517791748s
Understandability | Number of label check for Bio2RDF::Gendr took 10.30176854133606s
Understandability | URI regex check for Bio2RDF::Gendr took 0.5546350479125977s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.259352445602417s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2792489528656006s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.25699901580810547s
Performance | Throughput check for Bio2RDF::Gendr took 10.901051759719849s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 77.79825472831726s
Verifiability | Contribs. check for Bio2RDF::Gendr took 2.045727252960205s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.344210147857666s
Interlinking | skos check for Bio2RDF::Gendr took 0.782172441482544s
Interlinking | skos check for Bio2RDF::Gendr took 0.3661527633666992s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2629680633544922s
Currency | Creation date check for Bio2RDF::Gendr took 0.5358257293701172s
Currency | Modification date check for Bio2RDF::Gendr took 0.5455095767974854s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 124.06705164909363s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.4300577640533447s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.26627659797668457s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.28856539726257324s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 18.005045413970947s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.9003939628601074s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6869106292724609s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.39763879776000977s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 71.28982996940613s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.452141761779785s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 12.646214962005615s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3649334907531738s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.603795289993286s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7107181549072266s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.5917870998382568s
Security | Sign check for Bio2RDF::Gendr took 0.30017852783203125s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 11.911325693130493s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.4007413387298584s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.507469177246094e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-gendr took 1089.8770785331726s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.4629664421081543s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0005693435668945312s
Extra | Recovery of all triples for Bio2RDF::Goa took 36.24232530593872s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2318346500396729s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.59133744239807s
Interoperability | New terms check for Bio2RDF::Goa took 42.89840483665466s
Versatility | Languages check for Bio2RDF::Goa took 60.26988172531128s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.28171753883361816s
Security | Check HTTPS for Bio2RDF::Goa took 0.1669769287109375s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.9911143779754639s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.320711612701416s
Availability | RDF dump link check for Bio2RDF::Goa took 6.444072961807251s
License | MR license check for Bio2RDF::Goa took 0.5509748458862305s
License | HR license check for Bio2RDF::Goa took 60.243005990982056s
Amount of data | Number of property check for Bio2RDF::Goa took 0.28863072395324707s
Understandability | Number of label check for Bio2RDF::Goa took 10.598989486694336s
Understandability | URI regex check for Bio2RDF::Goa took 0.5806212425231934s
Understandability | Vocabs check for Bio2RDF::Goa took 0.2775154113769531s
Verifiability | Authors check for Bio2RDF::Goa took 0.27613353729248047s
Verifiability | Publishers check for Bio2RDF::Goa took 0.25265955924987793s
Performance | Throughput check for Bio2RDF::Goa took 10.862285614013672s
Amount of data | Check the number of entities for Bio2RDF::Goa took 71.86655330657959s
Verifiability | Contribs. check for Bio2RDF::Goa took 0.2648277282714844s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.3641831874847412s
Interlinking | skos check for Bio2RDF::Goa took 0.985335111618042s
Interlinking | skos check for Bio2RDF::Goa took 0.348707914352417s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.266643762588501s
Currency | Creation date check for Bio2RDF::Goa took 0.5409238338470459s
Currency | Modification date check for Bio2RDF::Goa took 0.5633103847503662s
Rep.Conc. | URIs length for Bio2RDF::Goa took 121.16021537780762s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.43477535247802734s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2874114513397217s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.2844817638397217s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 17.443439960479736s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.9068615436553955s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6616322994232178s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.4595491886138916s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 70.85805749893188s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.3976857662200928s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 11.259486436843872s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.351794719696045s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.60267686843872s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.7012109756469727s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.39873600006103516s
Security | Sign check for Bio2RDF::Goa took 0.2592949867248535s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 11.771852254867554s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 1.0019886493682861s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.021770715713500977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 5.817413330078125e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-goa took 1093.6388368606567s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.46892237663269043s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0011265277862548828s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 36.25917148590088s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.281646966934204s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 52.54613256454468s
Interoperability | New terms check for Bio2RDF::Hgnc took 44.05488872528076s
Versatility | Languages check for Bio2RDF::Hgnc took 60.28904747962952s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2789928913116455s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15465164184570312s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.8265972137451172s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.37245678901672363s
Availability | RDF dump link check for Bio2RDF::Hgnc took 6.351583957672119s
License | MR license check for Bio2RDF::Hgnc took 0.6190032958984375s
License | HR license check for Bio2RDF::Hgnc took 60.24483799934387s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.2680034637451172s
Understandability | Number of label check for Bio2RDF::Hgnc took 10.856046199798584s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5863988399505615s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.27240562438964844s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2797560691833496s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.25394392013549805s
Performance | Throughput check for Bio2RDF::Hgnc took 10.546267032623291s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 76.96258759498596s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.2938966751098633s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.3524963855743408s
Interlinking | skos check for Bio2RDF::Hgnc took 0.7656683921813965s
Interlinking | skos check for Bio2RDF::Hgnc took 0.3608126640319824s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.27617311477661133s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5331032276153564s
Currency | Modification date check for Bio2RDF::Hgnc took 0.5310168266296387s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 121.17580604553223s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.4020721912384033s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.2824587821960449s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.275501012802124s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 19.37559700012207s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.9027717113494873s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.6597721576690674s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.41565847396850586s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 71.56560230255127s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.4824750423431396s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 11.647547006607056s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.3451948165893555s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.561665773391724s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7163577079772949s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.4057796001434326s
Security | Sign check for Bio2RDF::Hgnc took 0.27043890953063965s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 11.90555715560913s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.9877924919128418s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00013875961303710938s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1088.4518027305603s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.4715452194213867s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0008270740509033203s
Extra | Recovery of all triples for Bio2RDF::Homologene took 37.4340033531189s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2910950183868408s
Amount of data | Number of triples check for Bio2RDF::Homologene took 45.970980644226074s
Interoperability | New terms check for Bio2RDF::Homologene took 44.954615354537964s
Versatility | Languages check for Bio2RDF::Homologene took 60.247650146484375s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.26759791374206543s
Security | Check HTTPS for Bio2RDF::Homologene took 0.15683913230895996s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.9373030662536621s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.32799458503723145s
Availability | RDF dump link check for Bio2RDF::Homologene took 6.359468460083008s
License | MR license check for Bio2RDF::Homologene took 0.47365641593933105s
License | HR license check for Bio2RDF::Homologene took 60.232319593429565s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2571873664855957s
Understandability | Number of label check for Bio2RDF::Homologene took 10.106172323226929s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6005439758300781s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.2534809112548828s
Verifiability | Authors check for Bio2RDF::Homologene took 0.26560354232788086s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.28865838050842285s
Performance | Throughput check for Bio2RDF::Homologene took 10.614083766937256s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 74.27307152748108s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.30858850479125977s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.3655393123626709s
Interlinking | skos check for Bio2RDF::Homologene took 0.8314571380615234s
Interlinking | skos check for Bio2RDF::Homologene took 0.41913700103759766s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.3017761707305908s
Currency | Creation date check for Bio2RDF::Homologene took 0.5628342628479004s
Currency | Modification date check for Bio2RDF::Homologene took 0.5192184448242188s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 119.91387987136841s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.4206676483154297s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.27532482147216797s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.27456021308898926s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 17.00682258605957s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.901303768157959s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6836624145507812s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.4171755313873291s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 71.83150100708008s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.4530081748962402s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 12.022698640823364s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.3321046829223633s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.613858699798584s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7121620178222656s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.4911017417907715s
Security | Sign check for Bio2RDF::Homologene took 0.26023054122924805s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 11.441702604293823s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.9311530590057373s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 3.3855438232421875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 6.4849853515625e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-homologene took 1080.798288345337s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.2668139934539795s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-inoh took 3.777169942855835s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.45549798011779785s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.00057220458984375s
Extra | Recovery of all triples for Bio2RDF::Interpro took 34.19302177429199s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.285311222076416s
Amount of data | Number of triples check for Bio2RDF::Interpro took 43.62532138824463s
Interoperability | New terms check for Bio2RDF::Interpro took 42.72065544128418s
Versatility | Languages check for Bio2RDF::Interpro took 60.227200746536255s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2739274501800537s
Security | Check HTTPS for Bio2RDF::Interpro took 0.14042139053344727s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.8724758625030518s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.340639591217041s
Availability | RDF dump link check for Bio2RDF::Interpro took 6.28969931602478s
License | MR license check for Bio2RDF::Interpro took 0.47116756439208984s
License | HR license check for Bio2RDF::Interpro took 60.236507415771484s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2955756187438965s
Understandability | Number of label check for Bio2RDF::Interpro took 10.186633825302124s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5931656360626221s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.26890993118286133s
Verifiability | Authors check for Bio2RDF::Interpro took 0.2666184902191162s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.2698485851287842s
Performance | Throughput check for Bio2RDF::Interpro took 10.315146684646606s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 74.33819842338562s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.5632705688476562s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.36578941345214844s
Interlinking | skos check for Bio2RDF::Interpro took 0.7776763439178467s
Interlinking | skos check for Bio2RDF::Interpro took 0.3574211597442627s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.27548670768737793s
Currency | Creation date check for Bio2RDF::Interpro took 0.5199925899505615s
Currency | Modification date check for Bio2RDF::Interpro took 0.5552232265472412s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 121.48747396469116s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.43336939811706543s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.287708044052124s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.281494140625s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 17.6671462059021s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8986766338348389s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.6793208122253418s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.41097283363342285s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 71.14573860168457s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.4115071296691895s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 12.419062376022339s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.3618361949920654s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.55910348892212s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.6931319236755371s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 0.6205511093139648s
Security | Sign check for Bio2RDF::Interpro took 0.27083802223205566s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 10.705615520477295s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 1.2751550674438477s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010824203491210938s
Believability | Calculation of trust value for Bio2RDF::Interpro took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-interpro took 1080.2198181152344s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13503170013427734s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.2680659294128418s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020104408264160156s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.534027099609375e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-iproclass took 17.042879581451416s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.4755985736846924s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006935596466064453s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 36.80685043334961s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2882752418518066s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.677817583084106s
Interoperability | New terms check for Bio2RDF::Irefindex took 44.304832220077515s
Versatility | Languages check for Bio2RDF::Irefindex took 60.28832745552063s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.2747037410736084s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.15775346755981445s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 1.1220755577087402s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.3216562271118164s
Availability | RDF dump link check for Bio2RDF::Irefindex took 6.507815599441528s
License | MR license check for Bio2RDF::Irefindex took 0.7265276908874512s
License | HR license check for Bio2RDF::Irefindex took 60.262027740478516s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.276322603225708s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.160254955291748s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.6197524070739746s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.26538920402526855s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2934761047363281s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.27086830139160156s
Performance | Throughput check for Bio2RDF::Irefindex took 10.700898170471191s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 75.05775737762451s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 2.073723077774048s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3592197895050049s
Interlinking | skos check for Bio2RDF::Irefindex took 0.9084067344665527s
Interlinking | skos check for Bio2RDF::Irefindex took 0.35563111305236816s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.30029845237731934s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5171298980712891s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5214769840240479s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 121.41742420196533s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.4573187828063965s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2715625762939453s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.29630470275878906s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 18.804866790771484s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8937075138092041s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6611106395721436s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.47173118591308594s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 71.15609979629517s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.417933464050293s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 12.10387897491455s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.323519229888916s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.55493712425232s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.6965372562408447s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.5559015274047852s
Security | Sign check for Bio2RDF::Irefindex took 0.2917318344116211s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 11.2137770652771s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.9690959453582764s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.939338684082031e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1091.5063607692719s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.6918017864227295s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.01987004280090332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.437301635742188e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-kegg took 5.064741611480713s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2802302837371826s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.02055811882019043s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 2.9828386306762695s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.13132691383361816s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.26384687423706055s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-linkedspl took 9.710430383682251s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.4997987747192383s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005536079406738281s
Extra | Recovery of all triples for Bio2RDF::Lsr took 36.15177583694458s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2309215068817139s
Amount of data | Number of triples check for Bio2RDF::Lsr took 43.75221920013428s
Interoperability | New terms check for Bio2RDF::Lsr took 43.38132095336914s
Versatility | Languages check for Bio2RDF::Lsr took 60.23982501029968s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.2531099319458008s
Security | Check HTTPS for Bio2RDF::Lsr took 0.16727638244628906s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.8590836524963379s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3457200527191162s
Availability | RDF dump link check for Bio2RDF::Lsr took 6.3350818157196045s
License | MR license check for Bio2RDF::Lsr took 0.5325806140899658s
License | HR license check for Bio2RDF::Lsr took 60.25037622451782s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.26710939407348633s
Understandability | Number of label check for Bio2RDF::Lsr took 10.129576444625854s
Understandability | URI regex check for Bio2RDF::Lsr took 0.6798830032348633s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.27856969833374023s
Verifiability | Authors check for Bio2RDF::Lsr took 0.269519567489624s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.24821925163269043s
Performance | Throughput check for Bio2RDF::Lsr took 11.092750072479248s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 74.875896692276s
Verifiability | Contribs. check for Bio2RDF::Lsr took 0.5889487266540527s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3582477569580078s
Interlinking | skos check for Bio2RDF::Lsr took 0.9216244220733643s
Interlinking | skos check for Bio2RDF::Lsr took 0.3613259792327881s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.28758883476257324s
Currency | Creation date check for Bio2RDF::Lsr took 0.5693809986114502s
Currency | Modification date check for Bio2RDF::Lsr took 0.5226962566375732s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 120.97371315956116s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.43522024154663086s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.27002835273742676s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.27184414863586426s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 20.175190210342407s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.9036550521850586s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.6740679740905762s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.4125223159790039s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 70.7785758972168s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.4224181175231934s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 12.276633739471436s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3508367538452148s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.553298234939575s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7024738788604736s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.568138837814331s
Security | Sign check for Bio2RDF::Lsr took 0.283954381942749s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 11.372671365737915s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.4184799194335938s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.340576171875e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-lsr took 1095.8438436985016s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.46713924407958984s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0004062652587890625s
Extra | Recovery of all triples for Bio2RDF::Mesh took 34.14520883560181s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.233222484588623s
Amount of data | Number of triples check for Bio2RDF::Mesh took 44.10905385017395s
Interoperability | New terms check for Bio2RDF::Mesh took 45.77183699607849s
Versatility | Languages check for Bio2RDF::Mesh took 60.24590992927551s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.269028902053833s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15749812126159668s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.7534916400909424s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.34255290031433105s
Availability | RDF dump link check for Bio2RDF::Mesh took 6.249714374542236s
License | MR license check for Bio2RDF::Mesh took 0.5410416126251221s
License | HR license check for Bio2RDF::Mesh took 60.25984573364258s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.29052281379699707s
Understandability | Number of label check for Bio2RDF::Mesh took 10.860547065734863s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5524451732635498s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.2711312770843506s
Verifiability | Authors check for Bio2RDF::Mesh took 0.28349733352661133s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.24853849411010742s
Performance | Throughput check for Bio2RDF::Mesh took 10.848190307617188s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 72.20140266418457s
Verifiability | Contribs. check for Bio2RDF::Mesh took 2.075979232788086s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.39373064041137695s
Interlinking | skos check for Bio2RDF::Mesh took 1.066066026687622s
Interlinking | skos check for Bio2RDF::Mesh took 0.39067864418029785s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.29128241539001465s
Currency | Creation date check for Bio2RDF::Mesh took 0.5357880592346191s
Currency | Modification date check for Bio2RDF::Mesh took 0.5660507678985596s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 121.70387721061707s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.4319322109222412s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.28267383575439453s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2803785800933838s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 19.875030517578125s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.9070892333984375s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6636416912078857s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.4200115203857422s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 70.96042275428772s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.443355083465576s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 12.683228731155396s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3525969982147217s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.59633469581604s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.6981158256530762s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.600602388381958s
Security | Sign check for Bio2RDF::Mesh took 0.2815382480621338s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 10.789573431015015s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.5412847995758057s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 6.961822509765625e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-mesh took 1075.3560309410095s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.46996426582336426s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0003600120544433594s
Extra | Recovery of all triples for Bio2RDF::Mgi took 36.546369314193726s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2337181568145752s
Amount of data | Number of triples check for Bio2RDF::Mgi took 44.568710803985596s
Interoperability | New terms check for Bio2RDF::Mgi took 42.15702414512634s
Versatility | Languages check for Bio2RDF::Mgi took 60.27022957801819s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.27924036979675293s
Security | Check HTTPS for Bio2RDF::Mgi took 0.17179107666015625s
Interpretability | RDF structures check for Bio2RDF::Mgi took 1.0457465648651123s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.34539365768432617s
Availability | RDF dump link check for Bio2RDF::Mgi took 6.31104588508606s
License | MR license check for Bio2RDF::Mgi took 0.5162153244018555s
License | HR license check for Bio2RDF::Mgi took 60.252875328063965s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2732725143432617s
Understandability | Number of label check for Bio2RDF::Mgi took 10.177918195724487s
Understandability | URI regex check for Bio2RDF::Mgi took 0.6187722682952881s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.2610158920288086s
Verifiability | Authors check for Bio2RDF::Mgi took 0.2950570583343506s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.2798116207122803s
Performance | Throughput check for Bio2RDF::Mgi took 10.75010871887207s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 75.98150205612183s
Verifiability | Contribs. check for Bio2RDF::Mgi took 0.5730082988739014s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.36272215843200684s
Interlinking | skos check for Bio2RDF::Mgi took 0.9791908264160156s
Interlinking | skos check for Bio2RDF::Mgi took 0.3851308822631836s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2756376266479492s
Currency | Creation date check for Bio2RDF::Mgi took 0.5056576728820801s
Currency | Modification date check for Bio2RDF::Mgi took 0.5554440021514893s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 120.23162984848022s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.41919851303100586s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2910432815551758s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2693819999694824s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 18.141616582870483s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.9013252258300781s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6798198223114014s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.39782142639160156s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 70.29092192649841s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.413067102432251s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 11.502971649169922s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3517603874206543s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.57061290740967s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.7148196697235107s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 0.6057138442993164s
Security | Sign check for Bio2RDF::Mgi took 0.2878141403198242s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 8.001459121704102s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.874687910079956s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02028346061706543s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.72747802734375e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-mgi took 1087.6598579883575s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.4747328758239746s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0007178783416748047s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 35.862868785858154s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2435941696166992s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.84104013442993s
Interoperability | New terms check for Bio2RDF::Ncbigene took 44.723355531692505s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.27889442443848s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2757229804992676s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.1595754623413086s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.8567883968353271s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.327542781829834s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 6.3396971225738525s
License | MR license check for Bio2RDF::Ncbigene took 0.4836118221282959s
License | HR license check for Bio2RDF::Ncbigene took 60.26398038864136s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.27770185470581055s
Understandability | Number of label check for Bio2RDF::Ncbigene took 10.370407342910767s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.589287519454956s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2669205665588379s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.29537391662597656s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2595515251159668s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.11600375175476s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 73.87127041816711s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.2733438014984131s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.384166955947876s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.8138799667358398s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.9259333610534668s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.6839542388916016s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5367193222045898s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5303671360015869s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 121.95123267173767s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.43526649475097656s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.27967166900634766s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2921593189239502s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 17.48017930984497s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.9023964405059814s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.6716005802154541s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.3804774284362793s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 71.63716888427734s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.4457032680511475s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 11.892634391784668s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.3170156478881836s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.59014868736267s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7089588642120361s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.48679637908935547s
Security | Sign check for Bio2RDF::Ncbigene took 0.27132749557495117s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 11.190563917160034s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 1.3740079402923584s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.0202791690826416s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012040138244628906s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1092.3738811016083s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 1.3041017055511475s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0005464553833007812s
Extra | Recovery of all triples for Bio2RDF::Ndc took 37.481600284576416s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2895448207855225s
Amount of data | Number of triples check for Bio2RDF::Ndc took 44.501821994781494s
Interoperability | New terms check for Bio2RDF::Ndc took 45.40096426010132s
Versatility | Languages check for Bio2RDF::Ndc took 60.27610445022583s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.26127123832702637s
Security | Check HTTPS for Bio2RDF::Ndc took 0.15499091148376465s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.9331233501434326s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.3302633762359619s
Availability | RDF dump link check for Bio2RDF::Ndc took 6.35303807258606s
License | MR license check for Bio2RDF::Ndc took 0.4900228977203369s
License | HR license check for Bio2RDF::Ndc took 60.25591850280762s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.27338242530822754s
Understandability | Number of label check for Bio2RDF::Ndc took 10.362414360046387s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5780494213104248s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.265186071395874s
Verifiability | Authors check for Bio2RDF::Ndc took 0.267345666885376s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2849435806274414s
Performance | Throughput check for Bio2RDF::Ndc took 10.899115324020386s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 75.35530757904053s
Verifiability | Contribs. check for Bio2RDF::Ndc took 0.4030735492706299s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.41494250297546387s
Interlinking | skos check for Bio2RDF::Ndc took 0.814481258392334s
Interlinking | skos check for Bio2RDF::Ndc took 0.3672666549682617s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2867472171783447s
Currency | Creation date check for Bio2RDF::Ndc took 0.6002533435821533s
Currency | Modification date check for Bio2RDF::Ndc took 0.5635850429534912s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 121.63726019859314s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4673500061035156s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2685275077819824s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.28400588035583496s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 18.06144690513611s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.9025363922119141s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6820855140686035s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.4242675304412842s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 71.01919198036194s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.4276320934295654s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 11.47147536277771s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.336651086807251s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.5449697971344s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7244229316711426s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.7684535980224609s
Security | Sign check for Bio2RDF::Ndc took 0.2567288875579834s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 11.722538709640503s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 1.4272375106811523s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 5.3882598876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ndc took 1082.9447605609894s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.264606237411499s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-netpath took 5.355509281158447s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13095998764038086s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005414485931396484s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.68831467628479s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-nextprot took 4.54852557182312s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.4989790916442871s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0007631778717041016s
Extra | Recovery of all triples for Bio2RDF::Omim took 35.75837206840515s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2690372467041016s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.296735763549805s
Interoperability | New terms check for Bio2RDF::Omim took 44.35563516616821s
Versatility | Languages check for Bio2RDF::Omim took 60.28348708152771s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.26158690452575684s
Security | Check HTTPS for Bio2RDF::Omim took 0.15832805633544922s
Interpretability | RDF structures check for Bio2RDF::Omim took 1.1026809215545654s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.35337233543395996s
Availability | RDF dump link check for Bio2RDF::Omim took 6.29375147819519s
License | MR license check for Bio2RDF::Omim took 0.5062365531921387s
License | HR license check for Bio2RDF::Omim took 60.25066328048706s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2727365493774414s
Understandability | Number of label check for Bio2RDF::Omim took 10.206888198852539s
Understandability | URI regex check for Bio2RDF::Omim took 0.5857336521148682s
Understandability | Vocabs check for Bio2RDF::Omim took 0.26308679580688477s
Verifiability | Authors check for Bio2RDF::Omim took 0.29538559913635254s
Verifiability | Publishers check for Bio2RDF::Omim took 0.27384233474731445s
Performance | Throughput check for Bio2RDF::Omim took 11.091968774795532s
Amount of data | Check the number of entities for Bio2RDF::Omim took 74.67831015586853s
Verifiability | Contribs. check for Bio2RDF::Omim took 2.0511107444763184s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.39645981788635254s
Interlinking | skos check for Bio2RDF::Omim took 0.9614737033843994s
Interlinking | skos check for Bio2RDF::Omim took 0.3743867874145508s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.27394795417785645s
Currency | Creation date check for Bio2RDF::Omim took 0.548316478729248s
Currency | Modification date check for Bio2RDF::Omim took 0.539665937423706s
Rep.Conc. | URIs length for Bio2RDF::Omim took 124.45606136322021s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4057598114013672s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.2642796039581299s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2656824588775635s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 18.955007553100586s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.9018959999084473s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6622142791748047s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.396960973739624s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 70.08637619018555s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.4398632049560547s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 11.77592420578003s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.3520183563232422s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.612377643585205s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7271227836608887s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 1.36149001121521s
Security | Sign check for Bio2RDF::Omim took 0.2738306522369385s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 10.078879117965698s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.6111502647399902s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.02019977569580078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001251697540283203s
Believability | Calculation of trust value for Bio2RDF::Omim took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 1115.356069803238s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.267692565917969e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.7199873924255371s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.01994609832763672s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.1961669921875e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 4.922329902648926s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.47088122367858887s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0006322860717773438s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 35.3980188369751s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2525880336761475s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 44.024813652038574s
Interoperability | New terms check for Bio2RDF::Orphanet took 43.01752305030823s
Versatility | Languages check for Bio2RDF::Orphanet took 60.25281834602356s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.2689831256866455s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.16808867454528809s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.7537796497344971s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.36907005310058594s
Availability | RDF dump link check for Bio2RDF::Orphanet took 6.350273370742798s
License | MR license check for Bio2RDF::Orphanet took 0.5740394592285156s
License | HR license check for Bio2RDF::Orphanet took 60.24829983711243s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.27386021614074707s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.213185548782349s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.6382770538330078s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.27870988845825195s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.2939453125s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.26309704780578613s
Performance | Throughput check for Bio2RDF::Orphanet took 11.011927366256714s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 73.4864091873169s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.574162483215332s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.34665775299072266s
Interlinking | skos check for Bio2RDF::Orphanet took 0.7385485172271729s
Interlinking | skos check for Bio2RDF::Orphanet took 0.38109660148620605s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.2911522388458252s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5629274845123291s
Currency | Modification date check for Bio2RDF::Orphanet took 0.5277106761932373s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 121.40848445892334s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.43926501274108887s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2788560390472412s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2750844955444336s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 16.85107445716858s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.890009880065918s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6848063468933105s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.4443683624267578s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 71.186105966568s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.446739673614502s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 11.765660285949707s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3096380233764648s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.629496574401855s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.720083475112915s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.4081716537475586s
Security | Sign check for Bio2RDF::Orphanet took 0.5600183010101318s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 11.605685472488403s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.8400211334228516s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.020859241485595703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 7.581710815429688e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1075.1403412818909s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.13594794273376465s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.00033354759216308594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.7040445804595947s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.019801855087280273s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 10.34646487236023s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.4776012897491455s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0005640983581542969s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 36.02163076400757s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.2201039791107178s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 45.297199010849s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 43.089364767074585s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.24748730659485s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.2897450923919678s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.15879511833190918s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.9777328968048096s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3571751117706299s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 6.250690221786499s
License | MR license check for Bio2RDF::Pharmgkb took 0.4408755302429199s
License | HR license check for Bio2RDF::Pharmgkb took 60.26817464828491s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.2618134021759033s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.0709228515625s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5892243385314941s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.3021705150604248s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.4084205627441406s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.28583216667175293s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.112581014633179s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 76.98929405212402s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.2872920036315918s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.3626081943511963s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.7453329563140869s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3289787769317627s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.29816770553588867s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5549321174621582s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5254871845245361s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 121.35701823234558s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.44315576553344727s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2803821563720703s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.290820837020874s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 18.023096799850464s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8961870670318604s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.688105583190918s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.680001974105835s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 71.10240912437439s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.3800737857818604s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 12.03501009941101s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.3037338256835938s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.5489456653595s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7032148838043213s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 0.48496246337890625s
Security | Sign check for Bio2RDF::Pharmgkb took 0.2674379348754883s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 10.618541240692139s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.5037872791290283s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02019357681274414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 8.559226989746094e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1103.9612803459167s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2536334991455078s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 4.660327911376953s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 7.987022399902344e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.2521541118621826s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 5.7220458984375e-06s
INFO | --- Analysis for bio2rdf-pid took 4.272300958633423s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.27147960662841797s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.24249267578125e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 2.8543598651885986s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.4873318672180176s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0005440711975097656s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 34.848411083221436s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.269376516342163s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 43.805739641189575s
Interoperability | New terms check for Bio2RDF::Pubmed took 42.67784070968628s
Versatility | Languages check for Bio2RDF::Pubmed took 60.25075912475586s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.2509136199951172s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.15789389610290527s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 0.7864875793457031s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.36150527000427246s
Availability | RDF dump link check for Bio2RDF::Pubmed took 6.425530672073364s
License | MR license check for Bio2RDF::Pubmed took 0.42580485343933105s
License | HR license check for Bio2RDF::Pubmed took 60.27125072479248s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.27387523651123047s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.482649803161621s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.6000568866729736s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.26979589462280273s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2878437042236328s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.24761390686035156s
Performance | Throughput check for Bio2RDF::Pubmed took 10.654690504074097s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 77.9608793258667s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.580150842666626s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.37832117080688477s
Interlinking | skos check for Bio2RDF::Pubmed took 1.0294151306152344s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3532369136810303s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.2722318172454834s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5203537940979004s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5266220569610596s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 120.87119364738464s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.5542993545532227s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.48863887786865234s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.4866325855255127s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 19.291608810424805s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8955225944519043s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6696963310241699s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.37929224967956543s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 71.32459664344788s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.450643301010132s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 12.262099266052246s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.3083868026733398s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.5352463722229s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.702601432800293s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.597705602645874s
Security | Sign check for Bio2RDF::Pubmed took 0.26857876777648926s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 10.079078912734985s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.41277647018432617s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020235061645507812s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00013136863708496094s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1081.2424845695496s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.25951051712036133s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.02009105682373047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.937980651855469e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-reactome took 3.7738704681396484s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.702200174331665s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020876169204711914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0008139610290527344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 6.842613220214844e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-rhea took 4.5961339473724365s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.1349489688873291s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.29196953773498535s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020493268966674805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.510185241699219e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-sabiork took 9.139579057693481s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.4687933921813965s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0006818771362304688s
Extra | Recovery of all triples for Bio2RDF::Sgd took 34.89759850502014s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.2440097332000732s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.875436544418335s
Interoperability | New terms check for Bio2RDF::Sgd took 46.68638634681702s
Versatility | Languages check for Bio2RDF::Sgd took 60.25374507904053s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.2888298034667969s
Security | Check HTTPS for Bio2RDF::Sgd took 0.1567075252532959s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.7091455459594727s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.34449338912963867s
Availability | RDF dump link check for Bio2RDF::Sgd took 6.326498746871948s
License | MR license check for Bio2RDF::Sgd took 0.6573715209960938s
License | HR license check for Bio2RDF::Sgd took 60.23262596130371s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.27361130714416504s
Understandability | Number of label check for Bio2RDF::Sgd took 10.492451190948486s
Understandability | URI regex check for Bio2RDF::Sgd took 0.6000800132751465s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.30965089797973633s
Verifiability | Authors check for Bio2RDF::Sgd took 0.3610856533050537s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.3588070869445801s
Performance | Throughput check for Bio2RDF::Sgd took 11.02120852470398s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 75.51909637451172s
Verifiability | Contribs. check for Bio2RDF::Sgd took 2.0481855869293213s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.3697657585144043s
Interlinking | skos check for Bio2RDF::Sgd took 0.9059195518493652s
Interlinking | skos check for Bio2RDF::Sgd took 0.34081172943115234s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2943542003631592s
Currency | Creation date check for Bio2RDF::Sgd took 0.5726301670074463s
Currency | Modification date check for Bio2RDF::Sgd took 1.5783238410949707s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 120.35304689407349s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.417910099029541s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2757120132446289s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.27904391288757324s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 18.309926509857178s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.9013280868530273s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6745395660400391s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.4306154251098633s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 70.81507921218872s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.8433287143707275s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 12.39187479019165s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.363769769668579s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.58817481994629s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.7058777809143066s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 1.3724887371063232s
Security | Sign check for Bio2RDF::Sgd took 0.2713015079498291s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 9.207359790802002s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.9297394752502441s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.02013850212097168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010538101196289062s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sgd took 1101.6685359477997s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.982948303222656e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0003306865692138672s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.24149465560913086s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020175457000732422s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.600120544433594e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 3.512380361557007s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.4691762924194336s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005559921264648438s
Extra | Recovery of all triples for Bio2RDF::Sider took 36.531951904296875s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2510578632354736s
Amount of data | Number of triples check for Bio2RDF::Sider took 43.585184812545776s
Interoperability | New terms check for Bio2RDF::Sider took 43.47218155860901s
Versatility | Languages check for Bio2RDF::Sider took 60.24855661392212s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.27828025817871094s
Security | Check HTTPS for Bio2RDF::Sider took 0.14550566673278809s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.96101975440979s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3724527359008789s
Availability | RDF dump link check for Bio2RDF::Sider took 6.399957656860352s
License | MR license check for Bio2RDF::Sider took 0.6754591464996338s
License | HR license check for Bio2RDF::Sider took 60.24928331375122s
Amount of data | Number of property check for Bio2RDF::Sider took 0.27806997299194336s
Understandability | Number of label check for Bio2RDF::Sider took 9.719934701919556s
Understandability | URI regex check for Bio2RDF::Sider took 0.611475944519043s
Understandability | Vocabs check for Bio2RDF::Sider took 0.26651430130004883s
Verifiability | Authors check for Bio2RDF::Sider took 0.26676225662231445s
Verifiability | Publishers check for Bio2RDF::Sider took 0.26175665855407715s
Performance | Throughput check for Bio2RDF::Sider took 10.81116795539856s
Amount of data | Check the number of entities for Bio2RDF::Sider took 74.42689752578735s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.3817870616912842s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.35336756706237793s
Interlinking | skos check for Bio2RDF::Sider took 0.9101941585540771s
Interlinking | skos check for Bio2RDF::Sider took 0.36847996711730957s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.27522730827331543s
Currency | Creation date check for Bio2RDF::Sider took 0.5110337734222412s
Currency | Modification date check for Bio2RDF::Sider took 0.505983829498291s
Rep.Conc. | URIs length for Bio2RDF::Sider took 123.04480314254761s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.4414684772491455s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.3056068420410156s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.27684998512268066s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 18.48191213607788s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.891481876373291s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6836538314819336s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4683670997619629s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 73.75268030166626s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.5610907077789307s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 12.460646152496338s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.3587744235992432s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.601322174072266s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7147860527038574s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.9308786392211914s
Security | Sign check for Bio2RDF::Sider took 0.27768397331237793s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 11.435814380645752s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.41587352752685547s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020373106002807617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.696846008300781e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-sider took 1090.032912015915s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.6854543685913086s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.019896268844604492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.9087066650390625e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-spike took 5.780714511871338s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.553794860839844e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2519373893737793s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.02017951011657715s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 3.886222839355469e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.621246337890625e-05s
INFO | --- Analysis for bio2rdf-taxon took 4.490584373474121s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.4701244831085205s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.00027632713317871094s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 36.4313428401947s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.2071218490600586s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.2396285533905s
Interoperability | New terms check for Bio2RDF::Taxonomy took 46.16447615623474s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.2952938079834s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2634885311126709s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.15193843841552734s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 1.2348451614379883s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.34085726737976074s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 6.366859674453735s
License | MR license check for Bio2RDF::Taxonomy took 0.4497079849243164s
License | HR license check for Bio2RDF::Taxonomy took 60.25581455230713s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.36855459213256836s
Understandability | Number of label check for Bio2RDF::Taxonomy took 9.925530910491943s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5656776428222656s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.28409695625305176s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.27535176277160645s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.2632255554199219s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.444790124893188s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 74.59048247337341s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.2930872440338135s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.36249804496765137s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.9332764148712158s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.39371371269226074s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2790389060974121s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5430176258087158s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5265836715698242s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 123.0408365726471s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4695713520050049s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.279813289642334s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.2686882019042969s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 17.762802124023438s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8979930877685547s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6966071128845215s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.41954970359802246s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 71.07684922218323s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.8022000789642334s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 11.756278038024902s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.3033342361450195s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.56917476654053s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7037293910980225s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.45177340507507324s
Security | Sign check for Bio2RDF::Taxonomy took 0.2999279499053955s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 9.97558069229126s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 1.0456173419952393s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.02021002769470215s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010347366333007812s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-taxonomy took 1095.2685871124268s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.13619637489318848s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0006337165832519531s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.3035595417022705s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.62396240234375e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 17.655004739761353s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.4779844284057617s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.00032591819763183594s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 37.32454705238342s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 5.585096836090088s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.142934799194336s
Interoperability | New terms check for Bio2RDF::Wormbase took 48.39963126182556s
Versatility | Languages check for Bio2RDF::Wormbase took 60.248610973358154s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.2575976848602295s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.1580047607421875s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 1.017911434173584s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3342008590698242s
Availability | RDF dump link check for Bio2RDF::Wormbase took 6.287356615066528s
License | MR license check for Bio2RDF::Wormbase took 0.4466867446899414s
License | HR license check for Bio2RDF::Wormbase took 60.237738847732544s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.2877624034881592s
Understandability | Number of label check for Bio2RDF::Wormbase took 11.311052799224854s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.6104283332824707s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.27342700958251953s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.26347994804382324s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.2613399028778076s
Performance | Throughput check for Bio2RDF::Wormbase took 11.67499828338623s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 76.49379634857178s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.2581751346588135s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3599367141723633s
Interlinking | skos check for Bio2RDF::Wormbase took 0.7947936058044434s
Interlinking | skos check for Bio2RDF::Wormbase took 0.36503028869628906s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2940521240234375s
Currency | Creation date check for Bio2RDF::Wormbase took 1.0407583713531494s
Currency | Modification date check for Bio2RDF::Wormbase took 1.0317976474761963s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 123.36270117759705s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.5658411979675293s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.769359827041626s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 1.2305693626403809s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 18.972150564193726s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8967974185943604s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.6685769557952881s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.7022244930267334s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 71.40491914749146s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4276630878448486s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 12.563754320144653s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.3648202419281006s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.6118369102478s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7059381008148193s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.4226069450378418s
Security | Sign check for Bio2RDF::Wormbase took 0.28255391120910645s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 10.894057750701904s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.8376312255859375s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 8.606910705566406e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1135.4513764381409s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.4345855712890625e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.6988356113433838s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020160198211669922s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.2159347534179688e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.152557373046875e-06s
INFO | --- Analysis for biografiasyvidas took 3.2859420776367188s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.2533457279205322s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.7234663963317871s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 9.655952453613281e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 5.0067901611328125e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 3.580617666244507s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 5.435943603515625e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2557077407836914s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.020166397094726562s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.0994415283203125e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for biolit took 2.9332523345947266s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.291534423828125e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.2619209289550781s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020175457000732422s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.981590270996094e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 6.198883056640625e-06s
INFO | --- Analysis for biolod-pdb took 8.411792755126953s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6387379169464111s
Availability | VoID file availability check for BioModels RDF took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.24225378036499023s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.695487976074219e-05s
Believability | Calculation of trust value for BioModels RDF took 7.3909759521484375e-06s
INFO | --- Analysis for biomodels-rdf took 3.6874568462371826s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.641052961349487s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006587505340576172s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.28295135498046875s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.023247718811035156s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0010867118835449219s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.933906555175781e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.152557373046875e-06s
INFO | --- Analysis for Biop took 10.745191097259521s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.410743713378906e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2466435432434082s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020275115966796875s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.647804260253906e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.62939453125e-06s
INFO | --- Analysis for Bioportal took 2.385892629623413s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.00039649009704589844s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2584705352783203s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006155967712402344s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-aao took 2.6694176197052s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.57763671875e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.24135041236877441s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02025127410888672s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.000286102294921875s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aba took 2.593423366546631s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2736659049987793s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014774799346923828s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-acgt took 2.5151290893554688s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.696846008300781e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.25209474563598633s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020843505859375s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0004067420959472656s
Believability | Calculation of trust value for Animal natural history and life history took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-adw took 2.517313003540039s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.24158716201782227s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0010066032409667969s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0005288124084472656s
Believability | Calculation of trust value for Anatomical Entity Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-aeo took 2.6329879760742188s
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.0005195140838623047s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2456049919128418s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009620189666748047s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aero took 2.5662708282470703s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.291534423828125e-05s
Availability | VoID file availability check for AI/RHEUM took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.24983668327331543s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003905296325683594s
Believability | Calculation of trust value for AI/RHEUM took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-air took 2.553408622741699s
Availability | SPARQL endpoint availability check for Amino Acid took 4.38690185546875e-05s
Availability | VoID file availability check for Amino Acid took 0.0011229515075683594s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.2594902515411377s
Reputation | Calculation of the PageRank for Amino Acid took 0.02045297622680664s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002486705780029297s
Believability | Calculation of trust value for Amino Acid took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.6086924076080322s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.76837158203125e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2598881721496582s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0003046989440917969s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-apo took 2.558434009552002s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 5.626678466796875e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.2767624855041504s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.021175146102905273s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00027561187744140625s
Believability | Calculation of trust value for African Traditional Medicine took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-atmo took 2.764543056488037s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.506111145019531e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.24719595909118652s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 9.250640869140625e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ato took 2.5761749744415283s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 5.555152893066406e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.26168155670166016s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013666152954101562s
Believability | Calculation of trust value for BioAssay Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bao took 2.6722960472106934s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2675361633300781s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.02050614356994629s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00037407875061035156s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.560267448425293s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 7.367134094238281e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.261122465133667s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003204345703125s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.590452194213867s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 9.012222290039062e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2706944942474365s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.021444082260131836s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.001375436782836914s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bdo took 2.6109511852264404s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.2670712471008301s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004868507385253906s
Believability | Calculation of trust value for Basic Formal Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bfo took 2.5905325412750244s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.3392181396484375e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.23932170867919922s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.01991558074951172s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007197856903076172s
Believability | Calculation of trust value for Bleeding History Phenotype took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bho took 2.5921146869659424s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.315376281738281e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.25510215759277344s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00042557716369628906s
Believability | Calculation of trust value for Bilateria anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bila took 2.6273303031921387s
Availability | SPARQL endpoint availability check for BIRNLex took 4.673004150390625e-05s
Availability | VoID file availability check for BIRNLex took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2638223171234131s
Reputation | Calculation of the PageRank for BIRNLex took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for BIRNLex took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.001461029052734375s
Believability | Calculation of trust value for BIRNLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-birnlex took 2.570751190185547s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.25563907623291016s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007634162902832031s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.541841506958008s
Availability | SPARQL endpoint availability check for BioPAX took 4.3392181396484375e-05s
Availability | VoID file availability check for BioPAX took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2686443328857422s
Reputation | Calculation of the PageRank for BioPAX took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.775161743164062e-05s
Believability | Calculation of trust value for BioPAX took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bp took 2.633756637573242s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.26727294921875s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003173351287841797s
Believability | Calculation of trust value for Biomedical Resource Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.5751800537109375s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.25440239906311035s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.00021839141845703125s
Believability | Calculation of trust value for Spatial Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-bspo took 2.566516637802124s
Availability | SPARQL endpoint availability check for BioTop took 4.410743713378906e-05s
Availability | VoID file availability check for BioTop took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for BioTop took 0.2541327476501465s
Reputation | Calculation of the PageRank for BioTop took 0.02011704444885254s
Interlinking | Calculation of Degree of Connection for BioTop took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006315708160400391s
Believability | Calculation of trust value for BioTop took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bt took 2.480762004852295s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.267692565917969e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.25334906578063965s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008587837219238281s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bto took 2.573376417160034s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.33113765716552734s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018069744110107422s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-canco took 3.093726396560669s
Availability | SPARQL endpoint availability check for CAO took 4.410743713378906e-05s
Availability | VoID file availability check for CAO took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for CAO took 0.26065778732299805s
Reputation | Calculation of the PageRank for CAO took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for CAO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0005714893341064453s
Believability | Calculation of trust value for CAO took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-cao took 2.6082379817962646s
Availability | SPARQL endpoint availability check for CareLex took 4.315376281738281e-05s
Availability | VoID file availability check for CareLex took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for CareLex took 0.2706329822540283s
Reputation | Calculation of the PageRank for CareLex took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for CareLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.935264587402344e-05s
Believability | Calculation of trust value for CareLex took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-carelex took 2.5223326683044434s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2624485492706299s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.00079345703125s
Believability | Calculation of trust value for Cell Cycle Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cco took 2.537564992904663s
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.0004150867462158203s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.2665364742279053s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0008499622344970703s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002875328063964844s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cdao took 2.5725183486938477s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.38690185546875e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2568080425262451s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0008485317230224609s
Believability | Calculation of trust value for Chemical entities of biological interest took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-chebi took 2.6189544200897217s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.410743713378906e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0011057853698730469s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.2677185535430908s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.00025153160095214844s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.6509902477264404s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.24968385696411133s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0008907318115234375s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0008623600006103516s
Believability | Calculation of trust value for Chemical Information Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cheminf took 2.653998374938965s
Availability | SPARQL endpoint availability check for Cell type took 4.38690185546875e-05s
Availability | VoID file availability check for Cell type took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Cell type took 0.26218724250793457s
Reputation | Calculation of the PageRank for Cell type took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for Cell type took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell type took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003914833068847656s
Believability | Calculation of trust value for Cell type took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cl took 2.6025118827819824s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.27710628509521484s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020248889923095703s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.000789642333984375s
Believability | Calculation of trust value for Cell Line Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-clo took 2.6606266498565674s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.26111459732055664s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.01999068260192871s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00016951560974121094s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cmo took 2.687593460083008s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2792627811431885s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02186417579650879s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0010728836059570312s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002589225769042969s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-cno took 2.617814540863037s
Availability | SPARQL endpoint availability check for Wheat trait took 4.673004150390625e-05s
Availability | VoID file availability check for Wheat trait took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.26721811294555664s
Reputation | Calculation of the PageRank for Wheat trait took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.7220458984375e-05s
Believability | Calculation of trust value for Wheat trait took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.5743494033813477s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.363059997558594e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2536635398864746s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003287792205810547s
Believability | Calculation of trust value for Cognitive Atlas took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cogat took 2.682616949081421s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.25661158561706543s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0008499622344970703s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007841587066650391s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cogpo took 2.6124632358551025s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2756328582763672s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004127025604248047s
Believability | Calculation of trust value for Current Procedural Terminology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-cpt took 2.530601978302002s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 8.249282836914062e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.29601168632507324s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.0203096866607666s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017292499542236328s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-csp took 2.971548557281494s
Availability | SPARQL endpoint availability check for COSTART took 4.4345855712890625e-05s
Availability | VoID file availability check for COSTART took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for COSTART took 0.26638054847717285s
Reputation | Calculation of the PageRank for COSTART took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for COSTART took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009772777557373047s
Believability | Calculation of trust value for COSTART took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cst took 2.6122543811798096s
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.0005252361297607422s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.25342798233032227s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.02043318748474121s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004987716674804688s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ctcae took 2.6290032863616943s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.220008850097656e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2752561569213867s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.02043747901916504s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.00043272972106933594s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ctx took 2.610517740249634s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.315376281738281e-05s
Availability | VoID file availability check for Dendritic cell took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.25316429138183594s
Reputation | Calculation of the PageRank for Dendritic cell took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00028705596923828125s
Believability | Calculation of trust value for Dendritic cell took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.537008285522461s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.553794860839844e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2788691520690918s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 9.107589721679688e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ddanat took 2.5819733142852783s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 7.891654968261719e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2582526206970215s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009920597076416016s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ddi took 2.6470894813537598s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 6.389617919921875e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.28000378608703613s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.082389831542969e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.6101062297821045s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.2565488815307617s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00015974044799804688s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.5703201293945312s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Human disease ontology took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.26164865493774414s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.000629425048828125s
Believability | Calculation of trust value for Human disease ontology took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-doid took 2.55492901802063s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.25498175621032715s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0007681846618652344s
Believability | Calculation of trust value for Electrocardiography Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ecg took 2.6072542667388916s
Availability | SPARQL endpoint availability check for Evidence codes took 7.033348083496094e-05s
Availability | VoID file availability check for Evidence codes took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.24239373207092285s
Reputation | Calculation of the PageRank for Evidence codes took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for Evidence codes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.361701965332031e-05s
Believability | Calculation of trust value for Evidence codes took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-eco took 2.5675525665283203s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.30014824867248535s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.001726388931274414s
Believability | Calculation of trust value for Experimental Factor Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-efo took 3.1422715187072754s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 4.291534423828125e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.2706480026245117s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020850419998168945s
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.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011627674102783203s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ehda took 2.6328117847442627s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.3392181396484375e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.26532793045043945s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007014274597167969s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.494884729385376s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.76837158203125e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.25674915313720703s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020830392837524414s
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.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005190372467041016s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.5972752571105957s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.315376281738281e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.2796785831451416s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.147125244140625e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-emap took 2.5992188453674316s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Environment Ontology took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.25489139556884766s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003960132598876953s
Believability | Calculation of trust value for Environment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-envo took 2.598557233810425s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.363059997558594e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00048828125s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2768135070800781s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020389556884765625s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00028514862060546875s
Believability | Calculation of trust value for Plant environmental conditions took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-eo took 2.622124671936035s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.2609832286834717s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.02081441879272461s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0010571479797363281s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0013756752014160156s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-ep took 2.5550310611724854s
Availability | SPARQL endpoint availability check for Epilepsy took 4.482269287109375e-05s
Availability | VoID file availability check for Epilepsy took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.27690935134887695s
Reputation | Calculation of the PageRank for Epilepsy took 0.02012491226196289s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.00012564659118652344s
Believability | Calculation of trust value for Epilepsy took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-epileponto took 2.6217539310455322s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.458427429199219e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.25345277786254883s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020455360412597656s
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.000736236572265625s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011167526245117188s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ero took 2.613340377807617s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 5.793571472167969e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2594788074493408s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011096000671386719s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ev took 2.5834126472473145s
Availability | SPARQL endpoint availability check for ExO took 4.57763671875e-05s
Availability | VoID file availability check for ExO took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for ExO took 0.2686338424682617s
Reputation | Calculation of the PageRank for ExO took 0.02119731903076172s
Interlinking | Calculation of Degree of Connection for ExO took 6.151199340820312e-05s
Interlinking | Calculation of Centrality for ExO took 0.0011742115020751953s
Interlinking | Calculation of Clustering coefficient for ExO took 0.0003445148468017578s
Believability | Calculation of trust value for ExO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-exo took 2.562483549118042s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2668492794036865s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011777877807617188s
Believability | Calculation of trust value for Fungal gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fao took 2.4853994846343994s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.6253204345703125e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0003218650817871094s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.2429335117340088s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00018405914306640625s
Believability | Calculation of trust value for Biological imaging methods took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbbi took 2.537889242172241s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.3392181396484375e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.26424551010131836s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020812034606933594s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006346702575683594s
Believability | Calculation of trust value for Drosophila gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbbt took 2.539076328277588s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 0.0001049041748046875s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2528419494628906s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004181861877441406s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-fbcv took 2.594897985458374s
Availability | SPARQL endpoint availability check for Drosophila development took 4.291534423828125e-05s
Availability | VoID file availability check for Drosophila development took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2770969867706299s
Reputation | Calculation of the PageRank for Drosophila development took 0.020246505737304688s
Interlinking | Calculation of Degree of Connection for Drosophila development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.482269287109375e-05s
Believability | Calculation of trust value for Drosophila development took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-fbdv took 2.594212293624878s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.57763671875e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0006480216979980469s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2472996711730957s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00037550926208496094s
Believability | Calculation of trust value for Fly taxonomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-fbsp took 2.6339712142944336s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.410743713378906e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0005621910095214844s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.27175259590148926s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00022172927856445312s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.5993549823760986s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.24150943756103516s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.02033686637878418s
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.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004096031188964844s
Believability | Calculation of trust value for Family Health History Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fhho took 2.533611297607422s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.3048582077026367s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.021178007125854492s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001081228256225586s
Believability | Calculation of trust value for Influenza Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-flu took 2.6505239009857178s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.26715922355651855s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020556926727294922s
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.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 7.033348083496094e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-fma took 2.637921094894409s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.26595568656921387s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020199060440063477s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00014019012451171875s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-fypo took 2.5885400772094727s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.2635676860809326s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.393692016601562e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.7249295711517334s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2694714069366455s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001633167266845703s
Believability | Calculation of trust value for General Formal Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo took 2.5949599742889404s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.172325134277344e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.27298974990844727s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020291566848754883s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0006101131439208984s
Believability | Calculation of trust value for General Formal Ontology: Biology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.562948226928711s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.172325134277344e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.2477560043334961s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.0200803279876709s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008411407470703125s
Believability | Calculation of trust value for Gene Ontology Extension took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.5315544605255127s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Gene Ontology took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2566556930541992s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008327960968017578s
Believability | Calculation of trust value for Gene Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.5105202198028564s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.267692565917969e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2557680606842041s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.9325485229492188e-05s
Believability | Calculation of trust value for Cereal Plant Development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro took 2.4711058139801025s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2591280937194824s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020110368728637695s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00042319297790527344s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.5272276401519775s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2594032287597656s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020213842391967773s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007688999176025391s
Believability | Calculation of trust value for Gene Regulation Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.544328212738037s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.25310659408569336s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02019977569580078s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005507469177246094s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hao took 2.471038818359375s
Availability | SPARQL endpoint availability check for HCPCS took 4.315376281738281e-05s
Availability | VoID file availability check for HCPCS took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2279222011566162s
Reputation | Calculation of the PageRank for HCPCS took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for HCPCS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00021457672119140625s
Believability | Calculation of trust value for HCPCS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.4982190132141113s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.315376281738281e-05s
Availability | VoID file availability check for Health Level Seven took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.2610905170440674s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012443065643310547s
Believability | Calculation of trust value for Health Level Seven took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hl7 took 2.5134308338165283s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.1961669921875e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.22788739204406738s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020131826400756836s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003299713134765625s
Believability | Calculation of trust value for HEALTH_INDICATORS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.4592812061309814s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.863739013671875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2908496856689453s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.7418136596679688e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hom took 2.5868260860443115s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.6253204345703125e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.26320433616638184s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020235300064086914s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.1948089599609375e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.6113979816436768s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26981163024902344s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020058393478393555s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006375312805175781s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.5721945762634277s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.24999475479125977s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02011728286743164s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001031637191772461s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hpio took 2.6321868896484375s
Availability | SPARQL endpoint availability check for HUGO took 4.363059997558594e-05s
Availability | VoID file availability check for HUGO took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for HUGO took 0.26073288917541504s
Reputation | Calculation of the PageRank for HUGO took 0.02022099494934082s
Interlinking | Calculation of Degree of Connection for HUGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.367134094238281e-05s
Believability | Calculation of trust value for HUGO took 1.6450881958007812e-05s
INFO | --- Analysis for bioportal-hugo took 2.5208375453948975s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.2773885726928711s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02112555503845215s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0010652542114257812s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0007531642913818359s
Believability | Calculation of trust value for Information Artifact Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-iao took 2.6454646587371826s
Availability | SPARQL endpoint availability check for ICD10 took 4.3392181396484375e-05s
Availability | VoID file availability check for ICD10 took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for ICD10 took 0.25117921829223633s
Reputation | Calculation of the PageRank for ICD10 took 0.020196199417114258s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0008027553558349609s
Believability | Calculation of trust value for ICD10 took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icd10 took 2.562238931655884s
Availability | SPARQL endpoint availability check for ICD10CM took 6.008148193359375e-05s
Availability | VoID file availability check for ICD10CM took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.2753417491912842s
Reputation | Calculation of the PageRank for ICD10CM took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for ICD10CM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006158351898193359s
Believability | Calculation of trust value for ICD10CM took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.614328145980835s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.363059997558594e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.27771496772766113s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020262956619262695s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00017333030700683594s
Believability | Calculation of trust value for ICD-10-PCS took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.5703108310699463s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 5.221366882324219e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2574045658111572s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.021538257598876953s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006628036499023438s
Believability | Calculation of trust value for International Classification of Diseases took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.5076656341552734s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.76837158203125e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.26257967948913574s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.000438690185546875s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.648920774459839s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.291534423828125e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2741851806640625s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02006840705871582s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012171268463134766s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icnp took 2.642136812210083s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.38690185546875e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2714071273803711s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020108461380004883s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00045990943908691406s
Believability | Calculation of trust value for International Classification of Primary Care took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-icpc took 2.6302764415740967s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.267692565917969e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.29678964614868164s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008563995361328125s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.6422317028045654s
Availability | SPARQL endpoint availability check for ICPS Network took 4.315376281738281e-05s
Availability | VoID file availability check for ICPS Network took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.25126004219055176s
Reputation | Calculation of the PageRank for ICPS Network took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00021958351135253906s
Believability | Calculation of trust value for ICPS Network took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-icps took 2.557770013809204s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2549622058868408s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0009624958038330078s
Believability | Calculation of trust value for Infectious Disease Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ido took 2.577265501022339s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.27080726623535156s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020058393478393555s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0012030601501464844s
Believability | Calculation of trust value for Brucellosis Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-idobru took 2.5173237323760986s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.2735595703125s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020137548446655273s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012750625610351562s
Believability | Calculation of trust value for Malaria Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-idomal took 2.5591747760772705s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.8160552978515625e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2622215747833252s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0002999305725097656s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-iev took 2.6488800048828125s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.291534423828125e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.24994349479675293s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00014829635620117188s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-imgt took 2.661841869354248s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.363059997558594e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.26322317123413086s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020323514938354492s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0004978179931640625s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-imr took 2.540313720703125s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.2560267448425293s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0007872581481933594s
Believability | Calculation of trust value for Interaction Network Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ino took 2.5271658897399902s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.5299530029296875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.27591705322265625s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020235061645507812s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.956390380859375e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.6253788471221924s
Availability | SPARQL endpoint availability check for IxnO took 4.291534423828125e-05s
Availability | VoID file availability check for IxnO took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for IxnO took 0.2677609920501709s
Reputation | Calculation of the PageRank for IxnO took 0.020102262496948242s
Interlinking | Calculation of Degree of Connection for IxnO took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.00018548965454101562s
Believability | Calculation of trust value for IxnO took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-ixno took 2.6236040592193604s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.458427429199219e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.27897071838378906s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020023107528686523s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0003647804260253906s
Believability | Calculation of trust value for SysMO-JERM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-jerm took 2.6037027835845947s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.2810850143432617s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-kisao took 2.621448040008545s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.172325134277344e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2566657066345215s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020194053649902344s
Believability | Calculation of trust value for Loggerhead nesting took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-lhn took 2.570549964904785s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Lipid Ontology took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.2529621124267578s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.0001983642578125s
Believability | Calculation of trust value for Lipid Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-lipro took 2.5813803672790527s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.1961669921875e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.2968623638153076s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018002986907958984s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lnc took 3.0386276245117188s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 5.459785461425781e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2676262855529785s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.019972801208496094s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006289482116699219s
Believability | Calculation of trust value for Mouse adult gross anatomy took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-ma took 2.5313832759857178s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.315376281738281e-05s
Availability | VoID file availability check for Multiple alignment took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.24800801277160645s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00019860267639160156s
Believability | Calculation of trust value for Multiple alignment took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mao took 2.7697157859802246s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.1961669921875e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2780148983001709s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006701946258544922s
Believability | Calculation of trust value for Minimal anatomical terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mat took 2.6985020637512207s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 7.82012939453125e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.2647581100463867s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020399808883666992s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 8.58306884765625e-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.0004134178161621094s
Believability | Calculation of trust value for Breast tissue cell lines took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.6072120666503906s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26879286766052246s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007426738739013672s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl took 2.6498143672943115s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cell line ontology took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26462745666503906s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014104843139648438s
Believability | Calculation of trust value for Cell line ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.666480541229248s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.3392181396484375e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.28462743759155273s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002338886260986328s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mcv took 2.709318161010742s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.2438507080078125e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.25599169731140137s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020168304443359375s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001704692840576172s
Believability | Calculation of trust value for Master Drug Data Base took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mddb took 2.642862319946289s
Availability | SPARQL endpoint availability check for MedDRA took 4.267692565917969e-05s
Availability | VoID file availability check for MedDRA took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for MedDRA took 0.24798035621643066s
Reputation | Calculation of the PageRank for MedDRA took 0.02001047134399414s
Interlinking | Calculation of Degree of Connection for MedDRA took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.001165151596069336s
Believability | Calculation of trust value for MedDRA took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mdr took 2.5484402179718018s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.267692565917969e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.2400374412536621s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008866786956787109s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.553485870361328s
Availability | SPARQL endpoint availability check for MeGO took 4.291534423828125e-05s
Availability | VoID file availability check for MeGO took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for MeGO took 0.2428290843963623s
Reputation | Calculation of the PageRank for MeGO took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for MeGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00014066696166992188s
Believability | Calculation of trust value for MeGO took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mego took 2.576448678970337s
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.0005972385406494141s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.3097364902496338s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02014446258544922s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017802715301513672s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mesh-owl took 2.989621877670288s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2681403160095215s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.02013564109802246s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0005886554718017578s
Believability | Calculation of trust value for Mental Functioning Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-mf took 2.5405452251434326s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.3392181396484375e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.26529598236083984s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005793571472167969s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mfo took 2.583918809890747s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005097389221191406s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.26833438873291016s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007328987121582031s
Believability | Calculation of trust value for Emotion Ontology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mfoem took 2.6520917415618896s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 5.7220458984375e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.2694106101989746s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010395050048828125s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mhc took 2.6152184009552s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.363059997558594e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2747375965118408s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0008301734924316406s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0007414817810058594s
Believability | Calculation of trust value for Protein-protein interaction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mi took 2.5566153526306152s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.1961669921875e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2547430992126465s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020148277282714844s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007326602935791016s
Believability | Calculation of trust value for Mosquito insecticide resistance took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-miro took 2.564016580581665s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 5.459785461425781e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.25691652297973633s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.0001323223114013672s
Believability | Calculation of trust value for Measurement Method Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mmo took 2.5210657119750977s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for MGED Ontology took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.2657194137573242s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003879070281982422s
Believability | Calculation of trust value for MGED Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mo took 2.502692222595215s
Availability | SPARQL endpoint availability check for Protein modification took 4.1961669921875e-05s
Availability | VoID file availability check for Protein modification took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Protein modification took 0.2665228843688965s
Reputation | Calculation of the PageRank for Protein modification took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021910667419433594s
Believability | Calculation of trust value for Protein modification took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mod took 2.580070734024048s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.673004150390625e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.24408316612243652s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006473064422607422s
Believability | Calculation of trust value for Mammalian phenotype took 3.814697265625e-06s
INFO | --- Analysis for bioportal-mp took 2.6030375957489014s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.220008850097656e-05s
Availability | VoID file availability check for Mouse pathology took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.2564716339111328s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00046181678771972656s
Believability | Calculation of trust value for Mouse pathology took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-mpath took 2.5282464027404785s
Availability | SPARQL endpoint availability check for Mass spectrometry took 5.435943603515625e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005719661712646484s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2693054676055908s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00035190582275390625s
Believability | Calculation of trust value for Mass spectrometry took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-ms took 2.6644251346588135s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 5.7697296142578125e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3042261600494385s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0018432140350341797s
Believability | Calculation of trust value for Medical Subject Headings took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-msh took 3.0066025257110596s
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.0002453327178955078s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.24021005630493164s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020426273345947266s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.0001690387725830078s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-mthch took 2.478996992111206s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.2732682228088379s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.000774383544921875s
Believability | Calculation of trust value for Natural Products Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-natpro took 2.63128662109375s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 5.030632019042969e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2527048587799072s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0007905960083007812s
Believability | Calculation of trust value for NCBI organismal classification took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.593782424926758s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 6.0558319091796875e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.31153297424316406s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.00200653076171875s
Believability | Calculation of trust value for NCI Thesaurus took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ncit took 3.0506670475006104s
Availability | SPARQL endpoint availability check for National Drug Data File took 0.000102996826171875s
Availability | VoID file availability check for National Drug Data File took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.25154733657836914s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006060600280761719s
Believability | Calculation of trust value for National Drug Data File took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nddf took 2.599942684173584s
Availability | SPARQL endpoint availability check for National Drug File took 7.62939453125e-05s
Availability | VoID file availability check for National Drug File took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2399439811706543s
Reputation | Calculation of the PageRank for National Drug File took 0.020583391189575195s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0011970996856689453s
Believability | Calculation of trust value for National Drug File took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.5999622344970703s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.3392181396484375e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.2513728141784668s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011289119720458984s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.572516679763794s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.27158474922180176s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.0206758975982666s
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.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006783008575439453s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-neomark took 2.606398582458496s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0005614757537841797s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.266948938369751s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.021824121475219727s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0009338855743408203s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00015401840209960938s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.653078556060791s
Availability | SPARQL endpoint availability check for NIFSTD took 4.38690185546875e-05s
Availability | VoID file availability check for NIFSTD took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3166992664337158s
Reputation | Calculation of the PageRank for NIFSTD took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for NIFSTD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.001873016357421875s
Believability | Calculation of trust value for NIFSTD took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nif took 3.1434249877929688s
Availability | SPARQL endpoint availability check for NIF Cell took 4.482269287109375e-05s
Availability | VoID file availability check for NIF Cell took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2561824321746826s
Reputation | Calculation of the PageRank for NIF Cell took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0013480186462402344s
Believability | Calculation of trust value for NIF Cell took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.5953781604766846s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.267692565917969e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2719600200653076s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013804435729980469s
Believability | Calculation of trust value for NIF Dysfunction took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.503532648086548s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2679426670074463s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005464553833007812s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-nigo took 2.660003900527954s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.6253204345703125e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.25661444664001465s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020328521728515625s
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.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005288124084472656s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nmr took 2.5987706184387207s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2624678611755371s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010395050048828125s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.567476749420166s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.27994585037231445s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011768341064453125s
Believability | Calculation of trust value for NanoParticle Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-npo took 2.5590882301330566s
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.0005283355712890625s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2817094326019287s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007262229919433594s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oae took 2.5522398948669434s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.887580871582031e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.2557401657104492s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.001424551010131836s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-obi took 2.520439386367798s
Availability | SPARQL endpoint availability check for OBOE took 4.315376281738281e-05s
Availability | VoID file availability check for OBOE took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for OBOE took 0.276308536529541s
Reputation | Calculation of the PageRank for OBOE took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OBOE took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011348724365234375s
Believability | Calculation of trust value for OBOE took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-oboe took 2.517071485519409s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.38690185546875e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2914712429046631s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007522106170654297s
Believability | Calculation of trust value for OBOE SBC took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.5953729152679443s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2560887336730957s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005846023559570312s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 3.814697265625e-06s
INFO | --- Analysis for bioportal-ocre took 2.6394317150115967s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 7.271766662597656e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2740747928619385s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008401870727539062s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-odgi took 2.6455602645874023s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.25459742546081543s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008394718170166016s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ogi took 2.625868558883667s
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.0004763603210449219s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2733604907989502s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020661115646362305s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00028586387634277344s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ogmd took 2.5862812995910645s
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.0004837512969970703s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2803006172180176s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.02083563804626465s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0007174015045166016s
Believability | Calculation of trust value for Ontology for General Medical Science took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ogms took 2.5447096824645996s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.4345855712890625e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2670269012451172s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011110305786132812s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-omim took 2.6016366481781006s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2690281867980957s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007839202880859375s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003750324249267578s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-omit took 2.599578380584717s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2706916332244873s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005812644958496094s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-omrse took 2.336940050125122s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.24428153038024902s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007507801055908203s
Believability | Calculation of trust value for Ontology of Data Mining took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-ontodm took 2.564331531524658s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.76837158203125e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0010228157043457031s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.24727630615234375s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02086353302001953s
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.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00025916099548339844s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.5344977378845215s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 7.700920104980469e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.28584766387939453s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0008361339569091797s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006654262542724609s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.641287326812744s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 5.0067901611328125e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.27329301834106445s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0008993148803710938s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-opl took 2.591336488723755s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.4345855712890625e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.27997469902038574s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008473396301269531s
Believability | Calculation of trust value for Phenotypic quality took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pato took 2.6245784759521484s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.863739013671875e-05s
Availability | VoID file availability check for Physician Data Query took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.25981712341308594s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0007882118225097656s
Believability | Calculation of trust value for Physician Data Query took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pdq took 2.5735435485839844s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.267692565917969e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.2502021789550781s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007693767547607422s
Believability | Calculation of trust value for Pediatric Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-pedterm took 2.5861337184906006s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.5299530029296875e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.26151347160339355s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.000186920166015625s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-peo took 2.612058162689209s
Availability | SPARQL endpoint availability check for PHARE took 4.38690185546875e-05s
Availability | VoID file availability check for PHARE took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for PHARE took 0.2653367519378662s
Reputation | Calculation of the PageRank for PHARE took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006344318389892578s
Believability | Calculation of trust value for PHARE took 3.814697265625e-06s
INFO | --- Analysis for bioportal-phare took 2.626155376434326s
Availability | SPARQL endpoint availability check for PKO_Re took 6.937980651855469e-05s
Availability | VoID file availability check for PKO_Re took 0.00048828125s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.24213910102844238s
Reputation | Calculation of the PageRank for PKO_Re took 0.02205181121826172s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016498565673828125s
Believability | Calculation of trust value for PKO_Re took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pko took 2.5821409225463867s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.57763671875e-05s
Availability | VoID file availability check for PMA 2010 took 0.00054931640625s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.26843738555908203s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009057521820068359s
Believability | Calculation of trust value for PMA 2010 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pma took 2.588040351867676s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.38690185546875e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.2526240348815918s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00015997886657714844s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pmr took 2.636765718460083s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.25951647758483887s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0003848075866699219s
Believability | Calculation of trust value for Plant Anatomy took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-po took 2.556950092315674s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 5.841255187988281e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2557802200317383s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.020636320114135742s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.771087646484375e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.619072675704956s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.482269287109375e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.26756906509399414s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004239082336425781s
Believability | Calculation of trust value for Plant Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.6435720920562744s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 5.1021575927734375e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.26927828788757324s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020436763763427734s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006394386291503906s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-pr took 2.595533847808838s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.220008850097656e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.27176570892333984s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002598762512207031s
Believability | Calculation of trust value for Proteomics data and process provenance took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-propreo took 2.6067841053009033s
Availability | SPARQL endpoint availability check for Pathway ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for Pathway ontology took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.26862382888793945s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00012445449829101562s
Believability | Calculation of trust value for Pathway ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pw took 2.564464569091797s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2561068534851074s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.021046161651611328s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-qibo took 2.618285655975342s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 5.745887756347656e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3001883029937744s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017473697662353516s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rcd took 2.995109796524048s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2785465717315674s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0008611679077148438s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012421607971191406s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rctontology took 2.6610875129699707s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.8160552978515625e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.2893402576446533s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.0001938343048095703s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-repo took 2.6878960132598877s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.267692565917969e-05s
Availability | VoID file availability check for Physico-chemical process took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.26029038429260254s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019049644470214844s
Believability | Calculation of trust value for Physico-chemical process took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-rex took 2.531187057495117s
Availability | SPARQL endpoint availability check for RadLex took 4.220008850097656e-05s
Availability | VoID file availability check for RadLex took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for RadLex took 0.2700934410095215s
Reputation | Calculation of the PageRank for RadLex took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015225410461425781s
Believability | Calculation of trust value for RadLex took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-rid took 2.581770420074463s
Availability | SPARQL endpoint availability check for RNA ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for RNA ontology took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2724144458770752s
Reputation | Calculation of the PageRank for RNA ontology took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005538463592529297s
Believability | Calculation of trust value for RNA ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-rnao took 2.562180280685425s
Availability | SPARQL endpoint availability check for Role Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Role Ontology took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2712879180908203s
Reputation | Calculation of the PageRank for Role Ontology took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00021004676818847656s
Believability | Calculation of trust value for Role Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-roleo took 2.583611011505127s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.265261173248291s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.02013850212097168s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017189979553222656s
Believability | Calculation of trust value for Rat Strain Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-rs took 2.5786292552948s
Availability | SPARQL endpoint availability check for RxNORM took 4.1961669921875e-05s
Availability | VoID file availability check for RxNORM took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2678539752960205s
Reputation | Calculation of the PageRank for RxNORM took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0005984306335449219s
Believability | Calculation of trust value for RxNORM took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.527630090713501s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.76837158203125e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2590198516845703s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.020787954330444336s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010302066802978516s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sao took 2.5337860584259033s
Availability | SPARQL endpoint availability check for Systems Biology took 4.315376281738281e-05s
Availability | VoID file availability check for Systems Biology took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.2511782646179199s
Reputation | Calculation of the PageRank for Systems Biology took 0.020732402801513672s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004584789276123047s
Believability | Calculation of trust value for Systems Biology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sbo took 2.6543893814086914s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.24644994735717773s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.000102996826171875s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-sbro took 2.546342611312866s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 5.3882598876953125e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0003535747528076172s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.25180578231811523s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013611316680908203s
Believability | Calculation of trust value for Sleep Domain Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-sdo took 2.459902048110962s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 6.103515625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.23668622970581055s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.020503759384155273s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003407001495361328s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sep took 2.5603830814361572s
Availability | SPARQL endpoint availability check for Student Health Record took 4.1961669921875e-05s
Availability | VoID file availability check for Student Health Record took 0.0010547637939453125s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.26458740234375s
Reputation | Calculation of the PageRank for Student Health Record took 0.020817279815673828s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004508495330810547s
Believability | Calculation of trust value for Student Health Record took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-shr took 2.728878974914551s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.601478576660156e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0008265972137451172s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.2701249122619629s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0011909008026123047s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sio took 9.49557614326477s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 7.081031799316406e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.24561285972595215s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00020122528076171875s
Believability | Calculation of trust value for Situation-Based Access Control took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sitbac took 2.6121973991394043s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.3392181396484375e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3042726516723633s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019001960754394531s
Believability | Calculation of trust value for SNOMED Clinical Terms took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-snomedct took 2.9894490242004395s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.26158857345581055s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0007042884826660156s
Believability | Calculation of trust value for SNP-Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-snpo took 2.5555739402770996s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.315376281738281e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2845611572265625s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005652904510498047s
Believability | Calculation of trust value for Sequence types and features took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.5692453384399414s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.2438507080078125e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.28218793869018555s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.001561880111694336s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-sopharm took 2.9827890396118164s
Availability | SPARQL endpoint availability check for SoyOntology took 4.4345855712890625e-05s
Availability | VoID file availability check for SoyOntology took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.25975489616394043s
Reputation | Calculation of the PageRank for SoyOntology took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for SoyOntology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00012755393981933594s
Believability | Calculation of trust value for SoyOntology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-soy took 2.5245485305786133s
Availability | SPARQL endpoint availability check for Spider Ontology took 5.245208740234375e-05s
Availability | VoID file availability check for Spider Ontology took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.25630974769592285s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003147125244140625s
Believability | Calculation of trust value for Spider Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-spd took 2.5627732276916504s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 5.6743621826171875e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2537050247192383s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020781517028808594s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00027942657470703125s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-spto took 2.6316184997558594s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.28026652336120605s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020722627639770508s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004401206970214844s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sso took 2.6423490047454834s
Availability | SPARQL endpoint availability check for Software Ontology took 4.673004150390625e-05s
Availability | VoID file availability check for Software Ontology took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2676241397857666s
Reputation | Calculation of the PageRank for Software Ontology took 0.02075028419494629s
Interlinking | Calculation of Degree of Connection for Software Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00039649009704589844s
Believability | Calculation of trust value for Software Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-swo took 2.651522159576416s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 5.888938903808594e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.23789453506469727s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.0002429485321044922s
Believability | Calculation of trust value for Tick gross anatomy took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-tads took 2.6258139610290527s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.24434518814086914s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008802413940429688s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-tao took 2.656041383743286s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 7.43865966796875e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.27181315422058105s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020980119705200195s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 9.512901306152344e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-taxrank took 2.6528048515319824s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.649162292480469e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.27365827560424805s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.224082946777344e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-teddy took 2.6288902759552s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Time Event Ontology took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.289447546005249s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020882368087768555s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0010232925415039062s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008351802825927734s
Believability | Calculation of trust value for Time Event Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-teo took 2.6521120071411133s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.2438507080078125e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.2838132381439209s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003795623779296875s
Believability | Calculation of trust value for Mosquito gross anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-tgma took 2.6335525512695312s
Availability | SPARQL endpoint availability check for thesaurus took 4.267692565917969e-05s
Availability | VoID file availability check for thesaurus took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for thesaurus took 0.28905153274536133s
Reputation | Calculation of the PageRank for thesaurus took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.000774383544921875s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.557868957519531e-05s
Believability | Calculation of trust value for thesaurus took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.6540732383728027s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 5.054473876953125e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.284013032913208s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00033783912658691406s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.6353490352630615s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2527608871459961s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008404254913330078s
Believability | Calculation of trust value for Translational Medicine Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tmo took 2.625612497329712s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2835066318511963s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015854835510253906s
Believability | Calculation of trust value for Plant Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-to took 2.613875150680542s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.27434372901916504s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001742839813232422s
Believability | Calculation of trust value for TOK_Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-tok took 2.6147615909576416s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.363059997558594e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2856729030609131s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.000186920166015625s
Believability | Calculation of trust value for Teleost taxonomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tto took 2.627689838409424s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.2930276393890381s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010209083557128906s
Believability | Calculation of trust value for Uber anatomy ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-uberon took 2.658193349838257s
Availability | SPARQL endpoint availability check for Units Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Units Ontology took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.2696082592010498s
Reputation | Calculation of the PageRank for Units Ontology took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002162456512451172s
Believability | Calculation of trust value for Units Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.6777660846710205s
Availability | SPARQL endpoint availability check for Units of measurement took 4.3392181396484375e-05s
Availability | VoID file availability check for Units of measurement took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.27611446380615234s
Reputation | Calculation of the PageRank for Units of measurement took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Units of measurement took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002853870391845703s
Believability | Calculation of trust value for Units of measurement took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-uo took 2.6103405952453613s
Availability | SPARQL endpoint availability check for VANDF took 4.267692565917969e-05s
Availability | VoID file availability check for VANDF took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for VANDF took 0.2935452461242676s
Reputation | Calculation of the PageRank for VANDF took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for VANDF took 4.100799560546875e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006682872772216797s
Believability | Calculation of trust value for VANDF took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-vandf took 2.611769437789917s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 5.53131103515625e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.26557397842407227s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00043201446533203125s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vao took 2.55908465385437s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.3392181396484375e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.25943875312805176s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006411075592041016s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-vhog took 2.6317739486694336s
Availability | SPARQL endpoint availability check for VIVO took 4.410743713378906e-05s
Availability | VoID file availability check for VIVO took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for VIVO took 0.2572653293609619s
Reputation | Calculation of the PageRank for VIVO took 0.020581960678100586s
Interlinking | Calculation of Degree of Connection for VIVO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003497600555419922s
Believability | Calculation of trust value for VIVO took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vivo took 2.6336066722869873s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.25133419036865234s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.001222848892211914s
Believability | Calculation of trust value for Vaccine Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-vo took 2.5423543453216553s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.24659967422485352s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002090930938720703s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vt took 2.6177480220794678s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.458427429199219e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.260953426361084s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.00048613548278808594s
Believability | Calculation of trust value for C. elegans gross anatomy took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-wbbt took 2.440235137939453s
Availability | SPARQL endpoint availability check for C. elegans development took 4.2438507080078125e-05s
Availability | VoID file availability check for C. elegans development took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2524538040161133s
Reputation | Calculation of the PageRank for C. elegans development took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for C. elegans development took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.601478576660156e-05s
Believability | Calculation of trust value for C. elegans development took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-wbls took 2.5676229000091553s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.363059997558594e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2712726593017578s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020628690719604492s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 9.131431579589844e-05s
Believability | Calculation of trust value for C. elegans phenotype took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.6326005458831787s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 5.340576171875e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.24768781661987305s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020249128341674805s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005793571472167969s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-who took 2.639399766921997s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 4.5299530029296875e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.2666294574737549s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.00067138671875s
Believability | Calculation of trust value for Xenopus anatomy and development took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-xao took 2.6080000400543213s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.00040841102600097656s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.28604912757873535s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00024437904357910156s
Believability | Calculation of trust value for Experimental Conditions Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-xco took 2.5448179244995117s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 9.107589721679688e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2858700752258301s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002703666687011719s
Believability | Calculation of trust value for Yeast phenotypes took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-ypo took 2.674647808074951s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.5299530029296875e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.25975871086120605s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007700920104980469s
Believability | Calculation of trust value for Zebrafish anatomy and development took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-zfa took 2.6206538677215576s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.3392181396484375e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0007967948913574219s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2710251808166504s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 5.9604644775390625e-06s
INFO | --- Analysis for Bioportal_link took 3.763263463973999s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.45738792419433594s
Availability | VoID file availability check for BioSamples RDF took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.24880051612854004s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02026057243347168s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 5.936622619628906e-05s
Believability | Calculation of trust value for BioSamples RDF took 5.245208740234375e-06s
INFO | --- Analysis for biosamples-rdf took 3.4094605445861816s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 1.0304920673370361s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0003514289855957031s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2949397563934326s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011324882507324219s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for bis-linked-data took 3.465319871902466s
Availability | SPARQL endpoint availability check for Bitzi took 4.124641418457031e-05s
Availability | VoID file availability check for Bitzi took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Bitzi took 0.2514634132385254s
Reputation | Calculation of the PageRank for Bitzi took 0.029357433319091797s
Interlinking | Calculation of Degree of Connection for Bitzi took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bitzi took 0.0014295578002929688s
Interlinking | Calculation of Clustering coefficient for Bitzi took 4.38690185546875e-05s
Believability | Calculation of trust value for Bitzi took 8.106231689453125e-06s
INFO | --- Analysis for bitzi took 2.9429562091827393s
Availability | SPARQL endpoint availability check for BizkaiSense took 5.3882598876953125e-05s
Availability | VoID file availability check for BizkaiSense took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.26587557792663574s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.1948089599609375e-05s
Believability | Calculation of trust value for BizkaiSense took 6.4373016357421875e-06s
INFO | --- Analysis for bizkaisense took 2.77234148979187s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.553794860839844e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.27602100372314453s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020177364349365234s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.8371810913085938e-05s
Believability | Calculation of trust value for blabla.itemlist took 6.9141387939453125e-06s
INFO | --- Analysis for blabla-itemlist took 2.885651111602783s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.124641418457031e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.26240062713623047s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.7179718017578125e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.62939453125e-06s
INFO | --- Analysis for blabla_itemlist took 2.8764779567718506s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.198883056640625e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0005791187286376953s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2839028835296631s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02022409439086914s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.933906555175781e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for bll-thesaurus took 3.613471269607544s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 0.4748115539550781s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.2601339817047119s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02023792266845703s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.341934204101562e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 8.344650268554688e-06s
INFO | --- Analysis for bluk-bnb took 10.162519454956055s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.27022743225097656s
Availability | VoID file availability check for Thesaurus BNCF took 0.0005548000335693359s
Extra | Recovery of all triples for Thesaurus BNCF took 48.42135453224182s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6828842163085938s
Amount of data | Number of triples check for Thesaurus BNCF took 0.6730725765228271s
Interoperability | New terms check for Thesaurus BNCF took 1.5171098709106445s
Versatility | Languages check for Thesaurus BNCF took 6.205715656280518s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.8973188400268555s
Security | Check HTTPS for Thesaurus BNCF took 0.0907433032989502s
Interpretability | RDF structures check for Thesaurus BNCF took 0.12213730812072754s
Versatility | Serialization formats check for Thesaurus BNCF took 0.13454866409301758s
Availability | RDF dump link check for Thesaurus BNCF took 0.1353898048400879s
License | MR license check for Thesaurus BNCF took 0.1239023208618164s
License | HR license check for Thesaurus BNCF took 0.2052628993988037s
Amount of data | Number of property check for Thesaurus BNCF took 0.12311434745788574s
Understandability | Number of label check for Thesaurus BNCF took 0.2613198757171631s
Understandability | URI regex check for Thesaurus BNCF took 0.25170350074768066s
Understandability | Vocabs check for Thesaurus BNCF took 0.12437057495117188s
Verifiability | Authors check for Thesaurus BNCF took 0.12579607963562012s
Verifiability | Publishers check for Thesaurus BNCF took 0.12563753128051758s
Performance | Throughput check for Thesaurus BNCF took 10.925017833709717s
Amount of data | Check the number of entities for Thesaurus BNCF took 4.291534423828125e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.1276562213897705s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.12101221084594727s
Interlinking | skos check for Thesaurus BNCF took 0.1696629524230957s
Interlinking | skos check for Thesaurus BNCF took 0.14232707023620605s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.12084341049194336s
Currency | Creation date check for Thesaurus BNCF took 0.25891685485839844s
Currency | Modification date check for Thesaurus BNCF took 0.25471949577331543s
Rep.Conc. | URIs length for Thesaurus BNCF took 25.23823118209839s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.11736917495727539s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.1588001251220703s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1195988655090332s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.158405542373657s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5203802585601807s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 4.053631544113159s
Consistency | Disjoint class check for Thesaurus BNCF took 0.13589715957641602s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.2312331199645996s
Consistency | Misplaced classes for Thesaurus BNCF took 7.063985586166382s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 9.422597408294678s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.610607385635376s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.3311879634857178s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4648890495300293s
Security | Sign check for Thesaurus BNCF took 0.12223935127258301s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.94940209388733s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.2875068187713623s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.295608520507812e-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 5.7220458984375e-06s
INFO | --- Analysis for bncf-ns took 192.09896540641785s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5433008670806885s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006692409515380859s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.0382936000823975s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4467806816101074s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.7232019901275635s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.114661455154419s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.322174072265625s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.9363808631896973s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2024238109588623s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.43834972381591797s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4548470973968506s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5539634227752686s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5528032779693604s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.315385818481445s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3111305236816406s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.5798592567443848s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6533358097076416s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.39862966537475586s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5865490436553955s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7817354202270508s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 12.189570903778076s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.033348083496094e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3242332935333252s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.44268798828125s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8699047565460205s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3829648494720459s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3903782367706299s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8522605895996094s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3375217914581299s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 17.782028675079346s
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.3267700672149658s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.26703381538391113s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.32373857498168945s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0114696025848389s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.024112701416015625s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.028650760650634766s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.36745381355285645s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.388868808746338s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.4062793254852295s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.6221022605895996s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.8945269584655762s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 14.768322229385376s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.032303571701049805s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.5474729537963867s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2753877639770508s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.50162148475647s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8180639743804932s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.021307945251464844s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.933906555175781e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6689300537109375e-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 422.79508900642395s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.38690185546875e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.26990222930908203s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020850658416748047s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.534027099609375e-05s
Believability | Calculation of trust value for Brazilian Politicians took 4.5299530029296875e-06s
INFO | --- Analysis for brazilian-politicians took 2.9013006687164307s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.38690185546875e-05s
Availability | VoID file availability check for BrazilianCities took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2583038806915283s
Reputation | Calculation of the PageRank for BrazilianCities took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.147125244140625e-05s
Believability | Calculation of trust value for BrazilianCities took 7.152557373046875e-06s
INFO | --- Analysis for braziliancities took 3.3392202854156494s
Availability | SPARQL endpoint availability check for Bricklink took 1.492908239364624s
Availability | VoID file availability check for Bricklink took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Bricklink took 0.27505040168762207s
Reputation | Calculation of the PageRank for Bricklink took 0.02020859718322754s
Interlinking | Calculation of Degree of Connection for Bricklink took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bricklink took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.747245788574219e-05s
Believability | Calculation of trust value for Bricklink took 6.198883056640625e-06s
INFO | --- Analysis for bricklink took 9.928931474685669s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.20459222793579s
Availability | VoID file availability check for British Museum Collection took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.279803991317749s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 2.8848648071289062e-05s
Believability | Calculation of trust value for British Museum Collection took 7.3909759521484375e-06s
INFO | --- Analysis for british-museum-collection took 72.70797491073608s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.2438507080078125e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2529478073120117s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.100799560546875e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 6.9141387939453125e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.8486223220825195s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.1484832763671875e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.2689690589904785s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.956390380859375e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 6.9141387939453125e-06s
INFO | --- Analysis for bsv took 3.3393547534942627s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.165925979614258s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.26009702682495117s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020090103149414062s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.2159347534179688e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.3909759521484375e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 6.904621839523315s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 5.602836608886719e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.278928279876709s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.02018117904663086s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.86102294921875e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 7.867813110351562e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.896901845932007s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.2438507080078125e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.26444363594055176s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 2.9802322387695312e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 7.152557373046875e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.8478775024414062s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.308758020401001s
Availability | VoID file availability check for business.data.gov.uk took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.25673604011535645s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.0204160213470459s
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.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.982948303222656e-05s
Believability | Calculation of trust value for business.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for business-data-gov-uk took 2.8410561084747314s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.5430893898010254s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0006866455078125s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.3079850673675537s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.5580663681030273s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.34894490242004395s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.7404577732086182s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 30.28219246864319s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3230001926422119s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.2722015380859375s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.4849097728729248s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.2794783115386963s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.3129158020019531s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.5500869750976562s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 18.911375522613525s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.4348299503326416s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.7646582126617432s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.4896974563598633s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.5075476169586182s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.41074395179748535s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.38379645347595215s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.318602800369263s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.104873657226562e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.2880117893218994s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.36884498596191406s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.38961052894592285s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.25441980361938477s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.25661635398864746s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.5553948879241943s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5147573947906494s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 2.005310535430908s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.2412548065185547s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.41419029235839844s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.3959517478942871s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 0.7444581985473633s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03382253646850586s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.02949810028076172s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.2962639331817627s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 0.8371708393096924s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.425276517868042s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 1.9379768371582031s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.332512378692627s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 1.9360790252685547s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.033444881439208984s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.28330206871032715s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.3220217227935791s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 889.0150339603424s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.4934577941894531s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.2874603271484375e-05s
INFO | --- Analysis for BVMC took 996.7689347267151s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.38690185546875e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.7009294033050537s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.019971370697021484s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.0040740966796875e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.3909759521484375e-06s
INFO | --- Analysis for cabbage took 3.7882368564605713s
Availability | SPARQL endpoint availability check for cablegate took 1.543409824371338s
Availability | VoID file availability check for cablegate took 0.0003559589385986328s
Completeness | Calculation of interlinking completeness for cablegate took 0.24003338813781738s
Reputation | Calculation of the PageRank for cablegate took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for cablegate took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for cablegate took 7.104873657226562e-05s
Believability | Calculation of trust value for cablegate took 7.3909759521484375e-06s
INFO | --- Analysis for cablegate took 18.04927372932434s
Availability | SPARQL endpoint availability check for Calames took 7.486343383789062e-05s
Availability | VoID file availability check for Calames took 0.0003662109375s
Completeness | Calculation of interlinking completeness for Calames took 0.2569394111633301s
Reputation | Calculation of the PageRank for Calames took 0.020315170288085938s
Interlinking | Calculation of Degree of Connection for Calames took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Calames took 3.3855438232421875e-05s
Believability | Calculation of trust value for Calames took 6.9141387939453125e-06s
INFO | --- Analysis for calames took 4.656017065048218s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.4287550449371338s
Availability | VoID file availability check for CaLiGraph took 0.0002338886260986328s
Extra | Recovery of all triples for CaLiGraph took 1.8502728939056396s
Performance | Total latancy measurement for CaLiGraph took 1.1343557834625244s
Amount of data | Number of triples check for CaLiGraph took 11.790475845336914s
Interoperability | New terms check for CaLiGraph took 2.107597827911377s
Versatility | Languages check for CaLiGraph took 60.30630278587341s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2603158950805664s
Security | Check HTTPS for CaLiGraph took 0.12854623794555664s
Interpretability | RDF structures check for CaLiGraph took 0.3260350227355957s
Versatility | Serialization formats check for CaLiGraph took 0.32696962356567383s
Availability | RDF dump link check for CaLiGraph took 0.25910210609436035s
License | MR license check for CaLiGraph took 0.34096717834472656s
License | HR license check for CaLiGraph took 60.318559408187866s
Amount of data | Number of property check for CaLiGraph took 0.2611720561981201s
Understandability | Number of label check for CaLiGraph took 3.2516751289367676s
Understandability | URI regex check for CaLiGraph took 0.5732252597808838s
Understandability | Vocabs check for CaLiGraph took 0.28263092041015625s
Verifiability | Authors check for CaLiGraph took 0.29956603050231934s
Verifiability | Publishers check for CaLiGraph took 0.2514023780822754s
Performance | Throughput check for CaLiGraph took 11.433407545089722s
Amount of data | Check the number of entities for CaLiGraph took 0.013453960418701172s
Verifiability | Contribs. check for CaLiGraph took 0.3013901710510254s
Interlinking | sameAs chians check for CaLiGraph took 0.6769881248474121s
Interlinking | skos check for CaLiGraph took 0.398639440536499s
Interlinking | skos check for CaLiGraph took 0.2309415340423584s
Timeliness | dataset update frequency check for CaLiGraph took 0.3161752223968506s
Currency | Creation date check for CaLiGraph took 0.5982770919799805s
Currency | Modification date check for CaLiGraph took 0.5677852630615234s
Rep.Conc. | URIs length for CaLiGraph took 61.18092703819275s
Interoperability | New vocabularies check for CaLiGraph took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.25389766693115234s
Accuracy | Check Functional Property for CaLiGraph took 0.25537705421447754s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.28859567642211914s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.7062087059020996s
Accuracy | Check White space in annotation for CaLiGraph took 0.027207136154174805s
Accuracy | Check Datatype consistency for CaLiGraph took 0.050565242767333984s
Consistency | Disjoint class check for CaLiGraph took 0.25211477279663086s
Consistency | Check Misplaced properties for CaLiGraph took 61.07194805145264s
Consistency | Misplaced classes for CaLiGraph took 0.4719827175140381s
Consistency | Check Ontology hijacking for CaLiGraph took 2.089974880218506s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2998955249786377s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.593501806259155s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.033518075942993164s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4530947208404541s
Security | Sign check for CaLiGraph took 0.33589768409729004s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.620086193084717s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.31666135787963867s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 2.9325485229492188e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 7.62939453125e-06s
INFO | --- Analysis for CaLiGraph took 1459.657140493393s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2679450511932373s
Availability | VoID file availability check for CaLiGraph took 0.0005741119384765625s
Extra | Recovery of all triples for CaLiGraph took 1.6822314262390137s
Performance | Total latancy measurement for CaLiGraph took 1.1752512454986572s
Amount of data | Number of triples check for CaLiGraph took 11.58458399772644s
Interoperability | New terms check for CaLiGraph took 2.1683483123779297s
Versatility | Languages check for CaLiGraph took 60.30548334121704s
Interpretability | Number of blank nodes check for CaLiGraph took 0.2512946128845215s
Security | Check HTTPS for CaLiGraph took 0.13939404487609863s
Interpretability | RDF structures check for CaLiGraph took 0.2621734142303467s
Versatility | Serialization formats check for CaLiGraph took 0.26206421852111816s
Availability | RDF dump link check for CaLiGraph took 0.2757377624511719s
License | MR license check for CaLiGraph took 0.2784128189086914s
License | HR license check for CaLiGraph took 60.31944417953491s
Amount of data | Number of property check for CaLiGraph took 0.26297950744628906s
Understandability | Number of label check for CaLiGraph took 3.0645089149475098s
Understandability | URI regex check for CaLiGraph took 0.5106048583984375s
Understandability | Vocabs check for CaLiGraph took 0.26734352111816406s
Verifiability | Authors check for CaLiGraph took 0.2592792510986328s
Verifiability | Publishers check for CaLiGraph took 0.25524091720581055s
Performance | Throughput check for CaLiGraph took 11.470924854278564s
Amount of data | Check the number of entities for CaLiGraph took 0.013928890228271484s
Verifiability | Contribs. check for CaLiGraph took 0.27338719367980957s
Interlinking | sameAs chians check for CaLiGraph took 0.6429693698883057s
Interlinking | skos check for CaLiGraph took 0.26250362396240234s
Interlinking | skos check for CaLiGraph took 0.23887324333190918s
Timeliness | dataset update frequency check for CaLiGraph took 0.27356743812561035s
Currency | Creation date check for CaLiGraph took 0.5227513313293457s
Currency | Modification date check for CaLiGraph took 0.5296251773834229s
Rep.Conc. | URIs length for CaLiGraph took 61.163610219955444s
Interoperability | New vocabularies check for CaLiGraph took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2615945339202881s
Accuracy | Check Functional Property for CaLiGraph took 0.2502706050872803s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.29894328117370605s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6203947067260742s
Accuracy | Check White space in annotation for CaLiGraph took 0.026406288146972656s
Accuracy | Check Datatype consistency for CaLiGraph took 0.049338340759277344s
Consistency | Disjoint class check for CaLiGraph took 0.26755642890930176s
Consistency | Check Misplaced properties for CaLiGraph took 61.085360050201416s
Consistency | Misplaced classes for CaLiGraph took 0.65303635597229s
Consistency | Check Ontology hijacking for CaLiGraph took 2.1401009559631348s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.3436264991760254s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.6545684337616s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.029999971389770508s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.4669647216796875s
Security | Sign check for CaLiGraph took 0.24670743942260742s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.173911571502686s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.9201347827911377s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 8.797645568847656e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 6.4373016357421875e-06s
INFO | --- Analysis for caligraph took 1472.3022561073303s
Availability | SPARQL endpoint availability check for can-link took 4.1961669921875e-05s
Availability | VoID file availability check for can-link took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for can-link took 0.7315726280212402s
Reputation | Calculation of the PageRank for can-link took 0.020872116088867188s
Interlinking | Calculation of Degree of Connection for can-link took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for can-link took 2.956390380859375e-05s
Believability | Calculation of trust value for can-link took 8.106231689453125e-06s
INFO | --- Analysis for can-link took 5.61197566986084s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.061040401458740234s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.7580044269561768s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 9.775161743164062e-06s
INFO | --- Analysis for cap-italy-rdf took 3.4622485637664795s
Availability | SPARQL endpoint availability check for person took 0.00020503997802734375s
Availability | VoID file availability check for person took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for person took 0.26867175102233887s
Reputation | Calculation of the PageRank for person took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for person took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for person took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for person took 2.8371810913085938e-05s
Believability | Calculation of trust value for person took 1.1444091796875e-05s
INFO | --- Analysis for card took 2.3365941047668457s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.1961669921875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2616562843322754s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020142793655395508s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 3.24249267578125e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 3.457326889038086s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.100799560546875e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.2831268310546875s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.8371810913085938e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 6.9141387939453125e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 3.7881863117218018s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.6664764881134033s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.00025916099548339844s
Extra | Recovery of all triples for Norway catch records dataset @PSNC took 119.59996247291565s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 1.009148359298706s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 11.99093246459961s
Interoperability | New terms check for Norway catch records dataset @PSNC took 13.13542890548706s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.24839901924133s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 2.711090326309204s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.25969386100769043s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 10.351911306381226s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.29648470878601074s
License | MR license check for Norway catch records dataset @PSNC took 0.5825541019439697s
License | HR license check for Norway catch records dataset @PSNC took 300.24999260902405s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.25649404525756836s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.328057050704956s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.6027786731719971s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.29039597511291504s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.20925140380859375s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.26108884811401367s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.533446788787842s
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.21163678169250488s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.1949923038482666s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4652104377746582s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4535403251647949s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 5.966925144195557s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.49918031692504883s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.22466397285461426s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 156.83441925048828s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.19853734970092773s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.2749307155609131s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.37775373458862305s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 41.35614800453186s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.721897602081299s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.6108877658843994s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.21132469177246094s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 85.3963234424591s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.328853130340576s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 34.32112669944763s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.3563098907470703s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 82.33425998687744s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.749039649963379s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5478711128234863s
Security | Sign check for Norway catch records dataset @PSNC took 0.8133382797241211s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 9.45298981666565s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 1.4721744060516357s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.020750045776367188s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.291534423828125e-05s
Interoperability | Check the re-using of existing vocabs for Norway catch records dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2269.4818921089172s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 7.796287536621094e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.2795097827911377s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011181831359863281s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.58306884765625e-06s
INFO | --- Analysis for ce4r took 382.4880976676941s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3610494136810303s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005006790161132812s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.4807658195495605s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.7431864738464355s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3931257724761963s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6626043319702148s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.15101671218872s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.178727388381958s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.30065441131591797s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14976263046264648s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.13988924026489258s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2500154972076416s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3294651508331299s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15824532508850098s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.25565171241760254s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.33057618141174316s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17752718925476074s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2508385181427002s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18403100967407227s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.753934621810913s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.009506225585938e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2404186725616455s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1588122844696045s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 1.0234806537628174s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1594853401184082s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1424868106842041s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.6061890125274658s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35134005546569824s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.0953330993652344s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16701197624206543s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.28766870498657227s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.32124805450439453s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.7082338333129883s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.02886819839477539s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.028249502182006836s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.40606117248535156s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.2104735374450684s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.0625855922698975s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3186697959899902s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.519493818283081s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03348684310913086s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.2344059944152832s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15596580505371094s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2833.5050411224365s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.6782069206237793s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020093679428100586s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.7206878662109375e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 6.9141387939453125e-06s
INFO | --- Analysis for ceo took 2958.0470762252808s
Availability | SPARQL endpoint availability check for Charging Stations took 5.555152893066406e-05s
Availability | VoID file availability check for Charging Stations took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.2982926368713379s
Reputation | Calculation of the PageRank for Charging Stations took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.2901763916015625e-05s
Believability | Calculation of trust value for Charging Stations took 7.3909759521484375e-06s
INFO | --- Analysis for charging-stations took 3.8796887397766113s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.220008850097656e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0006632804870605469s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.2781250476837158s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.170967102050781e-05s
Believability | Calculation of trust value for Chat Game corpus took 6.4373016357421875e-06s
INFO | --- Analysis for chat-game-corpus took 13.456302404403687s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.124641418457031e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00021791458129882812s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.6905059814453125s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.147125244140625e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.1920928955078125e-05s
INFO | --- Analysis for chebi took 4.877619743347168s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.8160552978515625e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0008003711700439453s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.6930310726165771s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020694971084594727s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.936622619628906e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 9.298324584960938e-06s
INFO | --- Analysis for chem2bio2rdf took 136.06388401985168s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.583543062210083s
Availability | VoID file availability check for ChEMBL RDF took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.2538795471191406s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.2928924560546875e-05s
Believability | Calculation of trust value for ChEMBL RDF took 6.67572021484375e-06s
INFO | --- Analysis for chembl-rdf took 4.8514838218688965s
Availability | SPARQL endpoint availability check for chemdb  dataset took 0.7944691181182861s
Availability | VoID file availability check for chemdb  dataset took 0.0002586841583251953s
Extra | Recovery of all triples for chemdb  dataset took 10.68105673789978s
Performance | Total latancy measurement for chemdb  dataset took 2.5296287536621094s
Amount of data | Number of triples check for chemdb  dataset took 0.5571553707122803s
Interoperability | New terms check for chemdb  dataset took 3.9574081897735596s
Versatility | Languages check for chemdb  dataset took 27.44114661216736s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5329897403717041s
Interpretability | RDF structures check for chemdb  dataset took 0.5364341735839844s
Versatility | Serialization formats check for chemdb  dataset took 1.5214250087738037s
Availability | RDF dump link check for chemdb  dataset took 0.8883984088897705s
License | MR license check for chemdb  dataset took 3.2814595699310303s
License | HR license check for chemdb  dataset took 4.07891321182251s
Amount of data | Number of property check for chemdb  dataset took 0.5434412956237793s
Understandability | Number of label check for chemdb  dataset took 5.439033508300781s
Understandability | URI regex check for chemdb  dataset took 1.778092384338379s
Understandability | Vocabs check for chemdb  dataset took 0.8536167144775391s
Verifiability | Authors check for chemdb  dataset took 1.220597505569458s
Verifiability | Publishers check for chemdb  dataset took 0.8279664516448975s
Performance | Throughput check for chemdb  dataset took 12.509395599365234s
Amount of data | Check the number of entities for chemdb  dataset took 7.319450378417969e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.8547863960266113s
Interlinking | sameAs chians check for chemdb  dataset took 1.1819453239440918s
Interlinking | skos check for chemdb  dataset took 2.2907590866088867s
Interlinking | skos check for chemdb  dataset took 0.5049400329589844s
Timeliness | dataset update frequency check for chemdb  dataset took 1.1663658618927002s
Currency | Creation date check for chemdb  dataset took 1.374725341796875s
Currency | Modification date check for chemdb  dataset took 1.0258092880249023s
Rep.Conc. | URIs length for chemdb  dataset took 3.3743183612823486s
Interoperability | New vocabularies check for chemdb  dataset took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5168514251708984s
Accuracy | Check Functional Property for chemdb  dataset took 0.8480625152587891s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.8314416408538818s
Accuracy | Check Empty annotation labels for chemdb  dataset took 2.9980530738830566s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030958175659179688s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.03301835060119629s
Consistency | Disjoint class check for chemdb  dataset took 0.6387012004852295s
Consistency | Check Misplaced properties for chemdb  dataset took 1.20487380027771s
Consistency | Misplaced classes for chemdb  dataset took 0.6088438034057617s
Consistency | Check Ontology hijacking for chemdb  dataset took 4.029128789901733s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.3443512916564941s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 2.0403685569763184s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03516745567321777s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5346992015838623s
Security | Sign check for chemdb  dataset took 2.142969846725464s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2707.8195326328278s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 1.4485344886779785s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 6.985664367675781e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb  dataset took 6.67572021484375e-06s
INFO | --- Analysis for chemdb-basicInfo took 3806.7292160987854s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5161139965057373s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.000255584716796875s
Extra | Recovery of all triples for chemdb estimated properties dataset took 10.582337856292725s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.5238208770751953s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.547100305557251s
Interoperability | New terms check for chemdb estimated properties dataset took 3.9472851753234863s
Versatility | Languages check for chemdb estimated properties dataset took 28.30838656425476s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5210573673248291s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5391898155212402s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.4170863628387451s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.80253005027771s
License | MR license check for chemdb estimated properties dataset took 2.6500515937805176s
License | HR license check for chemdb estimated properties dataset took 4.044636487960815s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5116922855377197s
Understandability | Number of label check for chemdb estimated properties dataset took 4.513598203659058s
Understandability | URI regex check for chemdb estimated properties dataset took 1.7366507053375244s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.7974851131439209s
Verifiability | Authors check for chemdb estimated properties dataset took 1.0810606479644775s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.6778702735900879s
Performance | Throughput check for chemdb estimated properties dataset took 13.871349573135376s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 0.00017571449279785156s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.6073734760284424s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 1.5560808181762695s
Interlinking | skos check for chemdb estimated properties dataset took 1.9908554553985596s
Interlinking | skos check for chemdb estimated properties dataset took 0.48978686332702637s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 1.1244871616363525s
Currency | Creation date check for chemdb estimated properties dataset took 1.3115684986114502s
Currency | Modification date check for chemdb estimated properties dataset took 1.0111737251281738s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 3.4015533924102783s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.495898962020874s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.7889022827148438s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7574331760406494s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 3.139880418777466s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030463218688964844s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03308916091918945s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.630673885345459s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.235201358795166s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6134943962097168s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 4.390500068664551s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.277414321899414s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 2.0322623252868652s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03230452537536621s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5211737155914307s
Security | Sign check for chemdb estimated properties dataset took 1.8526520729064941s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2742.0718727111816s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 1.0137906074523926s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020993471145629883s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.245208740234375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 6.67572021484375e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 3825.3409612178802s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5142576694488525s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002624988555908203s
Extra | Recovery of all triples for chemdb phase transition dataset took 10.58786153793335s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.509033203125s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.5594348907470703s
Interoperability | New terms check for chemdb phase transition dataset took 3.945737838745117s
Versatility | Languages check for chemdb phase transition dataset took 28.78415083885193s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5245294570922852s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.5335288047790527s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.4351906776428223s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8182802200317383s
License | MR license check for chemdb phase transition dataset took 2.8559131622314453s
License | HR license check for chemdb phase transition dataset took 4.1054017543792725s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5429644584655762s
Understandability | Number of label check for chemdb phase transition dataset took 4.901131629943848s
Understandability | URI regex check for chemdb phase transition dataset took 1.501176357269287s
Understandability | Vocabs check for chemdb phase transition dataset took 0.501713752746582s
Verifiability | Authors check for chemdb phase transition dataset took 1.1182363033294678s
Verifiability | Publishers check for chemdb phase transition dataset took 0.8038234710693359s
Performance | Throughput check for chemdb phase transition dataset took 13.969764947891235s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.271766662597656e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 1.7945866584777832s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.1645607948303223s
Interlinking | skos check for chemdb phase transition dataset took 2.0685620307922363s
Interlinking | skos check for chemdb phase transition dataset took 0.48241257667541504s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.109699010848999s
Currency | Creation date check for chemdb phase transition dataset took 1.3444361686706543s
Currency | Modification date check for chemdb phase transition dataset took 1.0313596725463867s
Rep.Conc. | URIs length for chemdb phase transition dataset took 3.3894436359405518s
Interoperability | New vocabularies check for chemdb phase transition dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.48735570907592773s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.7885041236877441s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.7782914638519287s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 3.090646982192993s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.031037330627441406s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03364968299865723s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.8269789218902588s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 1.2020704746246338s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.627122163772583s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 3.906087636947632s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.282853364944458s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.0117673873901367s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03285717964172363s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5309865474700928s
Security | Sign check for chemdb phase transition dataset took 2.1130576133728027s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2705.168740749359s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.5870163440704346s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 7.62939453125e-06s
INFO | --- Analysis for chemdb-phaseTransition took 3787.1725039482117s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5285665988922119s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.0002658367156982422s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 10.713757276535034s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.5236740112304688s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5629973411560059s
Interoperability | New terms check for chemdb thermochemistry dataset took 4.026642560958862s
Versatility | Languages check for chemdb thermochemistry dataset took 26.2732675075531s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.6228945255279541s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.5384705066680908s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.3892500400543213s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.8110511302947998s
License | MR license check for chemdb thermochemistry dataset took 3.0080058574676514s
License | HR license check for chemdb thermochemistry dataset took 4.113524913787842s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.5289533138275146s
Understandability | Number of label check for chemdb thermochemistry dataset took 5.014622211456299s
Understandability | URI regex check for chemdb thermochemistry dataset took 1.9348561763763428s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8058867454528809s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.0939521789550781s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.7928669452667236s
Performance | Throughput check for chemdb thermochemistry dataset took 12.485796689987183s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 7.295608520507812e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8120307922363281s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.1291120052337646s
Interlinking | skos check for chemdb thermochemistry dataset took 2.0266525745391846s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5016255378723145s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.0701148509979248s
Currency | Creation date check for chemdb thermochemistry dataset took 1.329688549041748s
Currency | Modification date check for chemdb thermochemistry dataset took 1.040581464767456s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 3.467028856277466s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.4982411861419678s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.7973294258117676s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.7701308727264404s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 3.197883367538452s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.03060603141784668s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03430795669555664s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.8126442432403564s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 1.2144241333007812s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6207489967346191s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 3.934227228164673s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.3396008014678955s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 2.0479812622070312s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03591275215148926s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5249664783477783s
Security | Sign check for chemdb thermochemistry dataset took 2.095012664794922s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2707.6620528697968s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 1.4609806537628174s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.02374100685119629s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.4836273193359375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 9.5367431640625e-07s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 9.5367431640625e-06s
INFO | --- Analysis for chemdb-thermochemistry took 3783.6113801002502s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 7.295608520507812e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0007154941558837891s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.25366640090942383s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020914316177368164s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for ChemPedia RDF took 5.7220458984375e-06s
INFO | --- Analysis for chempedia-rdf took 11.010545253753662s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.291534423828125e-05s
Availability | VoID file availability check for Chiman Maru took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.23563599586486816s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.218650817871094e-05s
Believability | Calculation of trust value for Chiman Maru took 5.7220458984375e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.745774745941162s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 0.6606180667877197s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.25577831268310547s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02058553695678711s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.218650817871094e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 8.58306884765625e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 5.795925140380859s
Availability | SPARQL endpoint availability check for Chronicling America took 4.553794860839844e-05s
Availability | VoID file availability check for Chronicling America took 0.0007092952728271484s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.26059889793395996s
Reputation | Calculation of the PageRank for Chronicling America took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00010204315185546875s
Believability | Calculation of trust value for Chronicling America took 1.1205673217773438e-05s
INFO | --- Analysis for chronicling-america took 6.519982814788818s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.8038532733917236s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0007166862487792969s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 135.90907645225525s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.7228996753692627s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.65895676612854s
Interoperability | New terms check for Cultural Heritage Thesaurus took 3.27947998046875s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.6741914749145508s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5611653327941895s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.33112025260925293s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.35798168182373047s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 12.270979404449463s
License | MR license check for Cultural Heritage Thesaurus took 0.30692291259765625s
License | HR license check for Cultural Heritage Thesaurus took 0.4197206497192383s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.28438711166381836s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.3563675880432129s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.6228582859039307s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2763969898223877s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.30483126640319824s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.3116569519042969s
Performance | Throughput check for Cultural Heritage Thesaurus took 12.276275157928467s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.20159912109375e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2649111747741699s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.27181267738342285s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3154890537261963s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.33811473846435547s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.30520057678222656s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.637744665145874s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.6426572799682617s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 11.596794366836548s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.28530049324035645s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.31105518341064453s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.29790449142456055s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.4109420776367188s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22850799560546875s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3396742343902588s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0496859550476074s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.2957479953765869s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 8.008614540100098s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.292405605316162s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00015735626220703125s
Security | Sign check for Cultural Heritage Thesaurus took 0.2687373161315918s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 290.5642569065094s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.8563535213470459s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.22786998748779297s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00012183189392089844s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for cht took 554.8553631305695s
Availability | SPARQL endpoint availability check for ciard-ring took 9.250640869140625e-05s
Availability | VoID file availability check for ciard-ring took 0.0005917549133300781s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.2675509452819824s
Reputation | Calculation of the PageRank for ciard-ring took 0.025691509246826172s
Interlinking | Calculation of Degree of Connection for ciard-ring took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.7206878662109375e-05s
Believability | Calculation of trust value for ciard-ring took 6.9141387939453125e-06s
INFO | --- Analysis for ciard-ring took 4.534395217895508s
Availability | SPARQL endpoint availability check for Cine Figure took 4.1961669921875e-05s
Availability | VoID file availability check for Cine Figure took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2513747215270996s
Reputation | Calculation of the PageRank for Cine Figure took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Cine Figure took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.506111145019531e-05s
Believability | Calculation of trust value for Cine Figure took 6.9141387939453125e-06s
INFO | --- Analysis for Cine_Figure took 3.248229503631592s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.189677000045776s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0007357597351074219s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.27033090591430664s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.601478576660156e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 174.14070296287537s
Availability | SPARQL endpoint availability check for CIPFA took 4.172325134277344e-05s
Availability | VoID file availability check for CIPFA took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for CIPFA took 0.7018382549285889s
Reputation | Calculation of the PageRank for CIPFA took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.62396240234375e-05s
Believability | Calculation of trust value for CIPFA took 4.5299530029296875e-06s
INFO | --- Analysis for cipfa took 4.4570348262786865s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.2971689701080322s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.27089738845825195s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0003998279571533203s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 6.4373016357421875e-06s
INFO | --- Analysis for ckan took 3.318389415740967s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 5.948164701461792s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.25847625732421875s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.021045684814453125s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for CLaSSES took 9.371967077255249s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.458427429199219e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.27060699462890625s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020415544509887695s
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.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.24249267578125e-05s
Believability | Calculation of trust value for Temples of the Classical World took 6.67572021484375e-06s
INFO | --- Analysis for classical_temples took 4.405809640884399s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.9888734817504883s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2699699401855469s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.01997828483581543s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.20159912109375e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.0067901611328125e-06s
INFO | --- Analysis for clean-energy-data-reegle took 8.828879833221436s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.274782657623291s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.724761962890625e-05s
Believability | Calculation of trust value for CLLD-afbo took 6.4373016357421875e-06s
INFO | --- Analysis for clld-afbo took 3.3871090412139893s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.25925374031066895s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.843971252441406e-05s
Believability | Calculation of trust value for CLLD-APICS took 6.67572021484375e-06s
INFO | --- Analysis for clld-apics took 3.3749828338623047s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 5.412101745605469e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.26354217529296875s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020093202590942383s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.458427429199219e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 7.152557373046875e-06s
INFO | --- Analysis for clld-ewave took 3.51847767829895s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 5.245208740234375e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.2570769786834717s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010466575622558594s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 6.4373016357421875e-06s
INFO | --- Analysis for clld-glottolog took 3.373945474624634s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.291534423828125e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0006442070007324219s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.27127861976623535s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020206212997436523s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.915496826171875e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.9141387939453125e-06s
INFO | --- Analysis for clld-phoible took 3.3957161903381348s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.23943662643432617s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.724761962890625e-05s
Believability | Calculation of trust value for CLLD-SAILS took 6.4373016357421875e-06s
INFO | --- Analysis for clld-sails took 3.5254058837890625s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.2438507080078125e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.26224279403686523s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.0108642578125e-05s
Believability | Calculation of trust value for CLLD-WALS took 7.3909759521484375e-06s
INFO | --- Analysis for clld-wals took 3.367034435272217s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.267692565917969e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.28446102142333984s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.939338684082031e-05s
Believability | Calculation of trust value for CLLD-WOLD took 6.67572021484375e-06s
INFO | --- Analysis for clld-wold took 3.5096287727355957s
Availability | SPARQL endpoint availability check for COD inventory took 4.1484832763671875e-05s
Availability | VoID file availability check for COD inventory took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for COD inventory took 0.255892276763916s
Reputation | Calculation of the PageRank for COD inventory took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for COD inventory took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COD inventory took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for COD inventory took 2.956390380859375e-05s
Believability | Calculation of trust value for COD inventory took 2.1696090698242188e-05s
INFO | --- Analysis for cod-inventory took 2.9033143520355225s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.11210751533508301s
Availability | VoID file availability check for Cooperation Databank took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.2654690742492676s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.552436828613281e-05s
Believability | Calculation of trust value for Cooperation Databank took 5.9604644775390625e-06s
INFO | --- Analysis for CoDa took 2.75152587890625s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.1484832763671875e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2514340877532959s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.0517578125e-05s
Believability | Calculation of trust value for CODE Endpoint took 8.106231689453125e-06s
INFO | --- Analysis for code-endpoint took 2.8273537158966064s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.5501682758331299s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.25560927391052246s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020209312438964844s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.9087066650390625e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 5.0067901611328125e-06s
INFO | --- Analysis for coins-openuplabs took 2.9823272228240967s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.010225772857666s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.24641060829162598s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02015829086303711s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.082389831542969e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 6.67572021484375e-06s
INFO | --- Analysis for CoLChina_sp2000 took 6.796107292175293s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.054105281829833984s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.25423336029052734s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.076957702636719e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for colinda took 2.453042984008789s
Availability | SPARQL endpoint availability check for CN  2012 took 25.519359350204468s
Availability | VoID file availability check for CN  2012 took 0.0007712841033935547s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.25626587867736816s
Reputation | Calculation of the PageRank for CN  2012 took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for CN  2012 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.933906555175781e-05s
Believability | Calculation of trust value for CN  2012 took 5.7220458984375e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 124.57034993171692s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.267692565917969e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.26530981063842773s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020348548889160156s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 6.9141387939453125e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 2.8491196632385254s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.3392181396484375e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2586669921875s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02020883560180664s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.8133392333984375e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.152557373046875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.803908109664917s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.1484832763671875e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.26801013946533203s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.123283386230469e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 6.9141387939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.8630096912384033s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.220008850097656e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.26817846298217773s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.8133392333984375e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 6.9141387939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.93518328666687s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.124641418457031e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.28283166885375977s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 2.8848648071289062e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.62939453125e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.9235188961029053s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.39812469482421875s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2639491558074951s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for CompHistSem took 3.818096160888672s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.221149444580078s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.00037407875061035156s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.25838661193847656s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.4809112548828125e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.3909759521484375e-06s
INFO | --- Analysis for comsode-d3-2 took 7.968104839324951s
Availability | SPARQL endpoint availability check for ConceptNet took 4.2438507080078125e-05s
Availability | VoID file availability check for ConceptNet took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.26390886306762695s
Reputation | Calculation of the PageRank for ConceptNet took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for ConceptNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 2.9802322387695312e-05s
Believability | Calculation of trust value for ConceptNet took 6.9141387939453125e-06s
INFO | --- Analysis for conceptnet took 2.879040241241455s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 5.1975250244140625e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2616138458251953s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020710468292236328s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0009715557098388672s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 0.000141143798828125s
Believability | Calculation of trust value for 2011 US Congress People took 5.4836273193359375e-06s
INFO | --- Analysis for congresspeople took 2.9147231578826904s
Availability | SPARQL endpoint availability check for MIMO took 0.29509663581848145s
Availability | VoID file availability check for MIMO took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for MIMO took 0.25574350357055664s
Reputation | Calculation of the PageRank for MIMO took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for MIMO took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.049041748046875e-05s
Believability | Calculation of trust value for MIMO took 6.9141387939453125e-06s
INFO | --- Analysis for CONNECTED took 3.5580239295959473s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.27208423614501953s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.02015233039855957s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.552436828613281e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.947432279586792s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.2438507080078125e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2529256343841553s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020610570907592773s
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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.9325485229492188e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 5.9604644775390625e-06s
INFO | --- Analysis for copac-library-catalogue took 2.788914203643799s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.553794860839844e-05s
Availability | VoID file availability check for Copyright Free Music took 0.00036025047302246094s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.2434859275817871s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.0279159545898438e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.67572021484375e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.643148899078369s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.482269287109375e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0005984306335449219s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.25066471099853516s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.699562072753906e-05s
Believability | Calculation of trust value for CopyrightTermBank took 6.67572021484375e-06s
INFO | --- Analysis for copyrighttermbank took 33.83471870422363s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.7635631561279297s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2818319797515869s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.910064697265625e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 6.9141387939453125e-06s
INFO | --- Analysis for core took 6.8612892627716064s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.6239473819732666s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.00025844573974609375s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 117.17539691925049s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.0104188919067383s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 8.246896266937256s
Interoperability | New terms check for Corine linked dataset @PSNC took 14.377394914627075s
Versatility | Languages check for Corine linked dataset @PSNC took 300.17587018013s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 3.1538398265838623s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.24100637435913086s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 8.984549760818481s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.24794840812683105s
License | MR license check for Corine linked dataset @PSNC took 0.3698740005493164s
License | HR license check for Corine linked dataset @PSNC took 300.22813534736633s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.2610197067260742s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.5303564071655273s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.7984955310821533s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.4397866725921631s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.20345187187194824s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.2801535129547119s
Performance | Throughput check for Corine linked dataset @PSNC took 11.451947450637817s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.581710815429688e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.20251870155334473s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.1809406280517578s
Interlinking | skos check for Corine linked dataset @PSNC took 0.44852709770202637s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4582223892211914s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.8452959060668945s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5171108245849609s
Currency | Modification date check for Corine linked dataset @PSNC took 0.24028372764587402s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 152.0228772163391s
Interoperability | New vocabularies check for Corine linked dataset @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Corine linked dataset @PSNC took 0.1976313591003418s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.30416393280029297s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.32915568351745605s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 42.65786004066467s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.690420627593994s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.6190035343170166s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.21009516716003418s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 85.01294803619385s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.399661302566528s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 33.924213886260986s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4230787754058838s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 88.24346852302551s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.8121492862701416s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.5639207363128662s
Security | Sign check for Corine linked dataset @PSNC took 0.45072507858276367s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 9.781721830368042s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.356924057006836s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.020843029022216797s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.4332275390625e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.0013580322265625e-05s
INFO | --- Analysis for Corine_linked_dataset took 2273.4575777053833s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.315376281738281e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.7157042026519775s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.2901763916015625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 7.62939453125e-06s
INFO | --- Analysis for corn took 4.684262037277222s
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.0002560615539550781s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2526977062225342s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.956390380859375e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 7.62939453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 3.699622392654419s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.100799560546875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.31470370292663574s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.2901763916015625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 7.867813110351562e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.997737407684326s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.2438507080078125e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.2801845073699951s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.02010941505432129s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 0.00013637542724609375s
Believability | Calculation of trust value for Cornetto1.2 took 7.152557373046875e-06s
INFO | --- Analysis for cornetto took 13.262949228286743s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.18920159339904785s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0004932880401611328s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 115.4610800743103s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.6343367099761963s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 135.521817445755s
Interoperability | New terms check for Corporate Body Named Authority List  took 94.10254669189453s
Versatility | Languages check for Corporate Body Named Authority List  took 300.0847444534302s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 1.188234806060791s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.29891037940979004s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.6269989013671875s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 2.729274034500122s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.34180235862731934s
License | MR license check for Corporate Body Named Authority List  took 0.2228105068206787s
License | HR license check for Corporate Body Named Authority List  took 300.0573396682739s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.18353652954101562s
Understandability | Number of label check for Corporate Body Named Authority List  took 6.761809587478638s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.2779724597930908s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.11013054847717285s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.1805121898651123s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.2323474884033203s
Performance | Throughput check for Corporate Body Named Authority List  took 21.103620052337646s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 7.319450378417969e-05s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.19677400588989258s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 9.050112009048462s
Interlinking | skos check for Corporate Body Named Authority List  took 0.40952134132385254s
Interlinking | skos check for Corporate Body Named Authority List  took 0.46151089668273926s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.2741997241973877s
Currency | Creation date check for Corporate Body Named Authority List  took 0.5070221424102783s
Currency | Modification date check for Corporate Body Named Authority List  took 0.24272632598876953s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 490.83928775787354s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.20063281059265137s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.18834590911865234s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.15987634658813477s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 30.23488140106201s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.148732900619507s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 6.402681589126587s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.17392587661743164s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 300.4819996356964s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.557282209396362s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 36.93390655517578s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 11.357329845428467s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 301.46867299079895s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 6.7882654666900635s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.4033982753753662s
Security | Sign check for Corporate Body Named Authority List  took 0.15121793746948242s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 4.556601524353027s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.2466745376586914s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.13053250312805176s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 0.0002257823944091797s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 2.86102294921875e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 7.3909759521484375e-06s
INFO | --- Analysis for corporate-body took 15312.287856578827s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.46403074264526367s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.26788949966430664s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.981590270996094e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for CorpusFibonacci took 16.098291873931885s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.124641418457031e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.724745512008667s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020743370056152344s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007998943328857422s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.361701965332031e-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 3.8346242904663086s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.1598513126373291s
Availability | VoID file availability check for Country Name Authority List took 0.0006308555603027344s
Extra | Recovery of all triples for Country Name Authority List took 80.38187527656555s
Performance | Total latancy measurement for Country Name Authority List took 0.6075019836425781s
Amount of data | Number of triples check for Country Name Authority List took 111.2754180431366s
Interoperability | New terms check for Country Name Authority List took 93.3782970905304s
Versatility | Languages check for Country Name Authority List took 300.0650579929352s
Interpretability | Number of blank nodes check for Country Name Authority List took 1.3892903327941895s
Security | Check HTTPS for Country Name Authority List took 0.233140230178833s
Interpretability | RDF structures check for Country Name Authority List took 0.3401331901550293s
Versatility | Serialization formats check for Country Name Authority List took 2.8823139667510986s
Availability | RDF dump link check for Country Name Authority List took 0.2390151023864746s
License | MR license check for Country Name Authority List took 0.24078583717346191s
License | HR license check for Country Name Authority List took 300.09728837013245s
Amount of data | Number of property check for Country Name Authority List took 0.20854520797729492s
Understandability | Number of label check for Country Name Authority List took 6.117953062057495s
Understandability | URI regex check for Country Name Authority List took 0.2688145637512207s
Understandability | Vocabs check for Country Name Authority List took 0.09601807594299316s
Verifiability | Authors check for Country Name Authority List took 0.14939451217651367s
Verifiability | Publishers check for Country Name Authority List took 0.18493127822875977s
Performance | Throughput check for Country Name Authority List took 10.8847017288208s
Amount of data | Check the number of entities for Country Name Authority List took 7.033348083496094e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.18904685974121094s
Interlinking | sameAs chians check for Country Name Authority List took 9.399023056030273s
Interlinking | skos check for Country Name Authority List took 0.2389659881591797s
Interlinking | skos check for Country Name Authority List took 0.45082807540893555s
Timeliness | dataset update frequency check for Country Name Authority List took 0.19396305084228516s
Currency | Creation date check for Country Name Authority List took 0.3480703830718994s
Currency | Modification date check for Country Name Authority List took 0.28073930740356445s
Rep.Conc. | URIs length for Country Name Authority List took 539.1821203231812s
Interoperability | New vocabularies check for Country Name Authority List took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.17423558235168457s
Accuracy | Check Functional Property for Country Name Authority List took 0.21361374855041504s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.193403959274292s
Accuracy | Check Empty annotation labels for Country Name Authority List took 30.185675621032715s
Accuracy | Check White space in annotation for Country Name Authority List took 3.1655690670013428s
Accuracy | Check Datatype consistency for Country Name Authority List took 9.8833327293396s
Consistency | Disjoint class check for Country Name Authority List took 0.1574394702911377s
Consistency | Check Misplaced properties for Country Name Authority List took 300.48449969291687s
Consistency | Misplaced classes for Country Name Authority List took 8.473721504211426s
Consistency | Check Ontology hijacking for Country Name Authority List took 32.40739846229553s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 11.929656982421875s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 301.47386145591736s
Conciseness | Check Extensional conciseness for Country Name Authority List took 9.73297119140625s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.42939186096191406s
Security | Sign check for Country Name Authority List took 0.14611196517944336s
Availability | Check URIs Dereferenciability for Country Name Authority List took 5.363628149032593s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.6194531917572021s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.22875356674194336s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 6.079673767089844e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.9073486328125e-06s
Believability | Calculation of trust value for Country Name Authority List took 5.245208740234375e-06s
INFO | --- Analysis for country-authority-list took 15480.546058893204s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.0876619815826416s
Availability | VoID file availability check for Courts thesaurus took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.7542903423309326s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02090740203857422s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.937980651855469e-05s
Believability | Calculation of trust value for Courts thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for courts-thesaurus took 3.451911449432373s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.6896836757659912s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2691526412963867s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.225440979003906e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 6.198883056640625e-06s
INFO | --- Analysis for Covid-on-the-Web took 7.4397406578063965s
Availability | SPARQL endpoint availability check for CPA 2008 took 25.841625928878784s
Availability | VoID file availability check for CPA 2008 took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.7068519592285156s
Reputation | Calculation of the PageRank for CPA 2008 took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.076957702636719e-05s
Believability | Calculation of trust value for CPA 2008 took 5.245208740234375e-06s
INFO | --- Analysis for cpa-2008 took 126.49839520454407s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.29425764083862305s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0006437301635742188s
Extra | Recovery of all triples for Cooperative Patent Classification took 37.797003984451294s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.9606614112854004s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.23772978782654s
Versatility | Languages check for Cooperative Patent Classification took 120.21556782722473s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.33551478385925s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.24352431297302246s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.20385003089904785s
Availability | RDF dump link check for Cooperative Patent Classification took 0.20797514915466309s
License | MR license check for Cooperative Patent Classification took 0.2501997947692871s
License | HR license check for Cooperative Patent Classification took 90.21798777580261s
Amount of data | Number of property check for Cooperative Patent Classification took 0.26303696632385254s
Understandability | Number of label check for Cooperative Patent Classification took 90.22705101966858s
Understandability | URI regex check for Cooperative Patent Classification took 0.6666741371154785s
Understandability | Vocabs check for Cooperative Patent Classification took 0.2525496482849121s
Verifiability | Authors check for Cooperative Patent Classification took 0.2537424564361572s
Verifiability | Publishers check for Cooperative Patent Classification took 0.22947001457214355s
Performance | Throughput check for Cooperative Patent Classification took 10.92563509941101s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.05718994140625e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.16644525527954102s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.1796267032623291s
Interlinking | skos check for Cooperative Patent Classification took 0.2645246982574463s
Interlinking | skos check for Cooperative Patent Classification took 0.19698357582092285s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.1710832118988037s
Currency | Creation date check for Cooperative Patent Classification took 0.549959659576416s
Currency | Modification date check for Cooperative Patent Classification took 0.408644437789917s
Rep.Conc. | URIs length for Cooperative Patent Classification took 156.43337440490723s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.2627091407775879s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 20.551950931549072s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.983945369720459s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.951128005981445s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.22754788398742676s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.41209816932678s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 74.47759413719177s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.5964233875274658s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.63274836540222s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.832670211791992s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.441023588180542s
Security | Sign check for Cooperative Patent Classification took 0.2534041404724121s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.7542343139648438s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 1.6320440769195557s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.021176815032958984s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 2.6226043701171875e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 7.152557373046875e-06s
INFO | --- Analysis for CPC took 1362.8978748321533s
Availability | SPARQL endpoint availability check for CPC 2008 took 24.952272415161133s
Availability | VoID file availability check for CPC 2008 took 0.0008463859558105469s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.7387058734893799s
Reputation | Calculation of the PageRank for CPC 2008 took 0.025939226150512695s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.528594970703125e-05s
Believability | Calculation of trust value for CPC 2008 took 5.245208740234375e-06s
INFO | --- Analysis for cpc-2008 took 125.09078121185303s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.458685159683228s
Availability | VoID file availability check for CPV  2003 took 0.0009438991546630859s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.33536720275878906s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020875930786132812s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0008082389831542969s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.696846008300781e-05s
Believability | Calculation of trust value for CPV  2003 took 5.0067901611328125e-06s
INFO | --- Analysis for cpv-2003 took 116.52653956413269s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.36618208885193s
Availability | VoID file availability check for CPV 2008 took 0.0008819103240966797s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.9344882965087891s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020984172821044922s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.7220458984375e-05s
Believability | Calculation of trust value for CPV 2008 took 5.7220458984375e-06s
INFO | --- Analysis for cpv-2008 took 130.43880033493042s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.7651765346527s
Availability | VoID file availability check for crowdsourcing-fb took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.25670838356018066s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.9114227294921875e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.9141387939453125e-06s
INFO | --- Analysis for crowdsourcing-fb took 535.7309584617615s
Availability | SPARQL endpoint availability check for CRTM took 4.1961669921875e-05s
Availability | VoID file availability check for CRTM took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for CRTM took 0.2506566047668457s
Reputation | Calculation of the PageRank for CRTM took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.361701965332031e-05s
Believability | Calculation of trust value for CRTM took 8.58306884765625e-06s
INFO | --- Analysis for crtm took 5.646312713623047s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 7.414817810058594e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.267805814743042s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 8.106231689453125e-06s
INFO | --- Analysis for crystal-eye took 4.17028284072876s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 7.234072685241699s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.7616994380950928s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 6.866455078125e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 4.291534423828125e-06s
INFO | --- Analysis for ctic-public-dataset took 44.94759202003479s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 4.696846008300781e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.25098252296447754s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.075599670410156e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 6.67572021484375e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 3.72983717918396s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.301546096801758s
Availability | VoID file availability check for CulturaLinkedData took 0.00048470497131347656s
Extra | Recovery of all triples for CulturaLinkedData took 166.43029260635376s
Performance | Total latancy measurement for CulturaLinkedData took 2.473069429397583s
Amount of data | Number of triples check for CulturaLinkedData took 3.378220796585083s
Interoperability | New terms check for CulturaLinkedData took 2.369138479232788s
Versatility | Languages check for CulturaLinkedData took 61.13791012763977s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.3096151351928711s
Interpretability | RDF structures check for CulturaLinkedData took 2.0836942195892334s
Versatility | Serialization formats check for CulturaLinkedData took 0.42832207679748535s
Availability | RDF dump link check for CulturaLinkedData took 0.25366806983947754s
License | MR license check for CulturaLinkedData took 2.4428021907806396s
License | HR license check for CulturaLinkedData took 61.27545142173767s
Amount of data | Number of property check for CulturaLinkedData took 0.13467717170715332s
Understandability | Number of label check for CulturaLinkedData took 0.08263373374938965s
Understandability | URI regex check for CulturaLinkedData took 0.6033551692962646s
Understandability | Vocabs check for CulturaLinkedData took 1.8809177875518799s
Verifiability | Authors check for CulturaLinkedData took 0.20566606521606445s
Verifiability | Publishers check for CulturaLinkedData took 1.8622937202453613s
Performance | Throughput check for CulturaLinkedData took 12.618668556213379s
Amount of data | Check the number of entities for CulturaLinkedData took 7.414817810058594e-05s
Verifiability | Contribs. check for CulturaLinkedData took 0.16556739807128906s
Interlinking | sameAs chians check for CulturaLinkedData took 0.0750586986541748s
Interlinking | skos check for CulturaLinkedData took 0.07587361335754395s
Interlinking | skos check for CulturaLinkedData took 0.07588887214660645s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.29463911056518555s
Currency | Creation date check for CulturaLinkedData took 0.3097705841064453s
Currency | Modification date check for CulturaLinkedData took 0.23233985900878906s
Rep.Conc. | URIs length for CulturaLinkedData took 79.28245377540588s
Interoperability | New vocabularies check for CulturaLinkedData took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 1.801410436630249s
Accuracy | Check Functional Property for CulturaLinkedData took 0.3335597515106201s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.18814444541931152s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 29.427082300186157s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6179277896881104s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.361886978149414s
Consistency | Disjoint class check for CulturaLinkedData took 0.07784485816955566s
Consistency | Check Misplaced properties for CulturaLinkedData took 8.917352437973022s
Consistency | Misplaced classes for CulturaLinkedData took 4.252948999404907s
Consistency | Check Ontology hijacking for CulturaLinkedData took 29.715744733810425s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.393789529800415s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.55238938331604s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3723258972167969s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.2901465892791748s
Security | Sign check for CulturaLinkedData took 0.9836156368255615s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 10.620521783828735s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.824023962020874s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021039962768554688s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.291534423828125e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.6689300537109375e-06s
Believability | Calculation of trust value for CulturaLinkedData took 7.867813110351562e-06s
INFO | --- Analysis for culturalinkeddata took 615.6184842586517s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.2211778163909912s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.23886561393737793s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020478010177612305s
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.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.933906555175781e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ares-or took 4.226174831390381s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.11282086372375488s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.7163152694702148s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.886222839355469e-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.088378190994263s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.10816502571105957s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0006089210510253906s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.25023794174194336s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007112026214599609s
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.245208740234375e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.2909610271453857s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.1175541877746582s
Availability | VoID file availability check for Integrated pollution registry took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.27950119972229004s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.814697265625e-05s
Believability | Calculation of trust value for Integrated pollution registry took 5.7220458984375e-06s
INFO | --- Analysis for cz-cenia-pollution took 2.866899251937866s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10660767555236816s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.2770535945892334s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.02039504051208496s
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.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.910064697265625e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.0013580322265625e-05s
INFO | --- Analysis for cz-contracts took 2.7991559505462646s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.1961669921875e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.2605578899383545s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.9325485229492188e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-courts took 2.916135549545288s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.11226511001586914s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005671977996826172s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.2675020694732666s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.6716461181640625e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-bans took 4.9541449546813965s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.1123955249786377s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0007541179656982422s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.25414586067199707s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.743171691894531e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.7111566066741943s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.10188007354736328s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.27569055557250977s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0008251667022705078s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 4.100799560546875e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.4836273193359375e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7696948051452637s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10574841499328613s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2667722702026367s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020966053009033203s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.2438507080078125e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 8.58306884765625e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.6634562015533447s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.10964322090148926s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005326271057128906s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2576265335083008s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020159482955932617s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.5762786865234375e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.847124338150024s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 10.179945468902588s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.25580716133117676s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.719329833984375e-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.864344835281372s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 10.11989712715149s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.2552969455718994s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.4332275390625e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 4.291534423828125e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 22.685346364974976s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.8050227165222168s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.25882887840270996s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.02008962631225586s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 4.291534423828125e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.6843421459198s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.3669261932373047s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.25620508193969727s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 4.267692565917969e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 3.2184648513793945s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.419208288192749s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0009362697601318359s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.6863281726837158s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.886222839355469e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.7781052589416504s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.42287230491638184s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.26026487350463867s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.172325134277344e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.3114700317382812s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.3944206237792969s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2560107707977295s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.021030902862548828s
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.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 4.1484832763671875e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.256448745727539s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.4200320243835449s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2870931625366211s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020279407501220703s
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.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.552436828613281e-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.117629289627075s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.4265308380126953s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.26546287536621094s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.3010599613189697s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.3776214122772217s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2750589847564697s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 4.124641418457031e-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.252434253692627s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.3852396011352539s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.3235163688659668s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0008561611175537109s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.2438507080078125e-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.5438857078552246s
Availability | SPARQL endpoint availability check for ATC groups took 0.10147285461425781s
Availability | VoID file availability check for ATC groups took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2755753993988037s
Reputation | Calculation of the PageRank for ATC groups took 0.020585298538208008s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0008711814880371094s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.843971252441406e-05s
Believability | Calculation of trust value for ATC groups took 7.152557373046875e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.7601888179779053s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.10787701606750488s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2559542655944824s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0211334228515625s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0010504722595214844s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 4.267692565917969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0728836059570312e-05s
INFO | --- Analysis for cz-fulfillments took 2.63653564453125s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.03888511657714844s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.27986717224121094s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020171403884887695s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.887580871582031e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 4.291534423828125e-06s
INFO | --- Analysis for cz-ic took 3.1355133056640625s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.18665719032287598s
Availability | VoID file availability check for List of Czech data boxes took 0.00054168701171875s
Extra | Recovery of all triples for List of Czech data boxes took 251.99682593345642s
Performance | Total latancy measurement for List of Czech data boxes took 0.6021654605865479s
Amount of data | Number of triples check for List of Czech data boxes took 68.12948894500732s
Interoperability | New terms check for List of Czech data boxes took 19.66038155555725s
Versatility | Languages check for List of Czech data boxes took 300.088326215744s
Interpretability | Number of blank nodes check for List of Czech data boxes took 4.5165183544158936s
Interpretability | RDF structures check for List of Czech data boxes took 0.20420193672180176s
Versatility | Serialization formats check for List of Czech data boxes took 1.5077896118164062s
Availability | RDF dump link check for List of Czech data boxes took 41.21978187561035s
License | MR license check for List of Czech data boxes took 0.39986586570739746s
License | HR license check for List of Czech data boxes took 300.1514902114868s
Amount of data | Number of property check for List of Czech data boxes took 0.36913466453552246s
Understandability | Number of label check for List of Czech data boxes took 8.575591802597046s
Understandability | URI regex check for List of Czech data boxes took 0.3614494800567627s
Understandability | Vocabs check for List of Czech data boxes took 0.19690394401550293s
Verifiability | Authors check for List of Czech data boxes took 0.2863306999206543s
Verifiability | Publishers check for List of Czech data boxes took 0.21140098571777344s
Performance | Throughput check for List of Czech data boxes took 10.432405233383179s
Amount of data | Check the number of entities for List of Czech data boxes took 3.1969664096832275s
Verifiability | Contribs. check for List of Czech data boxes took 1.3675472736358643s
Interlinking | sameAs chians check for List of Czech data boxes took 2.681729316711426s
Interlinking | skos check for List of Czech data boxes took 0.37259697914123535s
Interlinking | skos check for List of Czech data boxes took 0.16250109672546387s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.24899506568908691s
Currency | Creation date check for List of Czech data boxes took 1.0258252620697021s
Currency | Modification date check for List of Czech data boxes took 0.435762882232666s
Rep.Conc. | URIs length for List of Czech data boxes took 211.1189844608307s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.4857213497161865s
Accuracy | Check Functional Property for List of Czech data boxes took 0.1507892608642578s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.1533055305480957s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 95.781818151474s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.0910086631774902s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.636568546295166s
Consistency | Disjoint class check for List of Czech data boxes took 0.11541175842285156s
Consistency | Check Misplaced properties for List of Czech data boxes took 113.70014882087708s
Consistency | Misplaced classes for List of Czech data boxes took 7.9656291007995605s
Consistency | Check Ontology hijacking for List of Czech data boxes took 82.2295835018158s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.405808448791504s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 90.7581353187561s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.656742811203003s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 0.9922604560852051s
Security | Sign check for List of Czech data boxes took 0.16683244705200195s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 11.43670392036438s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.5399205684661865s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 5.1975250244140625e-05s
Believability | Calculation of trust value for List of Czech data boxes took 5.4836273193359375e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2451.3287818431854s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12595462799072266s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006606578826904297s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 246.19794273376465s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.5824768543243408s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 40.02908110618591s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 20.519428491592407s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.1220896244049s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 12.821270227432251s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10900545120239258s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.5414390563964844s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 40.583672761917114s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12016916275024414s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.0906677246094s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.689293622970581s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.543960094451904s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.3138878345489502s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.27094340324401855s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4588010311126709s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.24647951126098633s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.604203701019287s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.2832858562469482s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.5938639640808105s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.2923107147216797s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.35104799270629883s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10537457466125488s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.8768014907836914s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.61665415763855s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.32703375816345215s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 212.27623176574707s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.4811081886291504s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13020014762878418s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.09875655174255371s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 116.09675788879395s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.08782958984375s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6687357425689697s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.19692587852478027s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 103.51397609710693s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.072809219360352s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 74.40287947654724s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4416069984436035s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 95.41733169555664s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6735334396362305s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0083703994750977s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17247867584228516s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 520.7829813957214s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.547027349472046s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.021021366119384766s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.0531158447265625e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.7220458984375e-06s
INFO | --- Analysis for cz-nace took 2622.83198428154s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.31765270233154297s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0005881786346435547s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 187.2902729511261s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8113963603973389s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.29143857955932617s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5208864212036133s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 40.587138414382935s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.48461341857910156s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.27574872970581055s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.579526901245117s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5905778408050537s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.406339168548584s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.589261531829834s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17537832260131836s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5179953575134277s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3628716468811035s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18417811393737793s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2607154846191406s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.31014132499694824s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.691572189331055s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.510185241699219e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1737806797027588s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2250840663909912s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.34529757499694824s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1811506748199463s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8950047492980957s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.4121584892272949s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3814566135406494s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 60.59184217453003s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18511199951171875s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18088078498840332s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1933450698852539s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 45.867713928222656s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.4403228759765625s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.858572244644165s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2109971046447754s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0228369235992432s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.460192203521729s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 96.06842803955078s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.8173754215240479s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.2832224369049072s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.5149435997009277s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2461543083190918s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.468578577041626s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1056.3924140930176s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.2847402095794678s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.021091699600219727s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.790855407714844e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.814697265625e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.7220458984375e-06s
INFO | --- Analysis for cz-nkod took 67686.95295977592s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.2648472785949707s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0004153251647949219s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.7251286506652832s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.02014470100402832s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.4809112548828125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 5.245208740234375e-06s
INFO | --- Analysis for cz-orders took 4.063762664794922s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.20593786239624023s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.00031828880310058594s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 257.4447021484375s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.6326618194580078s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 55.952425956726074s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 17.78280234336853s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.15224981307983s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 3.9172983169555664s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.16595053672790527s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 0.8338828086853027s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 43.397623777389526s
License | MR license check for Institutions of public power of the Czech Republic took 0.38753819465637207s
License | HR license check for Institutions of public power of the Czech Republic took 300.1986393928528s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.41249752044677734s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 7.2637786865234375s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.4075438976287842s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.14866900444030762s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.19400262832641602s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.20783042907714844s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.609753608703613s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.259521484375s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.23519015312194824s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 0.5749526023864746s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.16417908668518066s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.12285232543945312s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.22352981567382812s
Currency | Creation date check for Institutions of public power of the Czech Republic took 0.6497993469238281s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.21477794647216797s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 203.46518111228943s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.5191831588745117s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.16212868690490723s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.16141533851623535s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 104.73996114730835s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.0761117935180664s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.6409332752227783s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.1474008560180664s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 99.8089325428009s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 8.387379884719849s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 85.54463267326355s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.3313424587249756s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 98.08836817741394s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.6604504585266113s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 1.0324630737304688s
Security | Sign check for Institutions of public power of the Czech Republic took 0.19044733047485352s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 4.076284885406494s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 1.0635604858398438s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 6.008148193359375e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ovm took 2449.1365258693695s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.19049620628356934s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.7152678966522217s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.337860107421875e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-ovm-agendas took 5.274512052536011s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 20.016821146011353s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.7843358516693115s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.628036499023438e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-ruian took 115.28900384902954s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.8149089813232422s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.3031961917877197s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.486343383789062e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 5.154242277145386s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.5287144184112549s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.27779102325439453s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sao-check-actions took 4.747509717941284s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.5207595825195312s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00039505958557128906s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.31151604652404785s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.075599670410156e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.911111354827881s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.13611721992492676s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.29378628730773926s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.266334533691406e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 7.3909759521484375e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 3.0253772735595703s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11954283714294434s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0006272792816162109s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.278292179107666s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.2901763916015625e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 3.0331075191497803s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.12034010887145996s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.29792141914367676s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 4.172325134277344e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-sidc-drugs took 3.077500820159912s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.14158225059509277s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0005519390106201172s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 252.43231558799744s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.6607978343963623s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 40.84288144111633s
Interoperability | New terms check for Summary types of Czech institutions of public power took 18.95743727684021s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.12420654296875s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 5.471395254135132s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.16657161712646484s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 1.6180620193481445s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 41.537086963653564s
License | MR license check for Summary types of Czech institutions of public power took 0.4641103744506836s
License | HR license check for Summary types of Czech institutions of public power took 300.17579340934753s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.16712141036987305s
Understandability | Number of label check for Summary types of Czech institutions of public power took 7.133564233779907s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.4282517433166504s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.20256280899047852s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.5648939609527588s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.24895954132080078s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.817906379699707s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.063985824584961s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.5678548812866211s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.789109468460083s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1761152744293213s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.12498044967651367s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.3298649787902832s
Currency | Creation date check for Summary types of Czech institutions of public power took 0.9725725650787354s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.48642516136169434s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 227.48697757720947s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.5410866737365723s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.12243843078613281s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.16519927978515625s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 119.09208464622498s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.078120470046997s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.696850299835205s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.12222576141357422s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 109.72805380821228s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 7.993657827377319s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 81.14876508712769s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.3465909957885742s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 84.25551128387451s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.6657207012176514s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 1.0227482318878174s
Security | Sign check for Summary types of Czech institutions of public power took 0.16038298606872559s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 553.8783674240112s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.5526072978973389s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.020987272262573242s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 2.6464462280273438e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 0.0001010894775390625s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.298324584960938e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2630.1763191223145s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.13917875289916992s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.7649242877960205s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.695487976074219e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 6.198883056640625e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 4.903578042984009s
Availability | SPARQL endpoint availability check for State funding providers took 0.12400126457214355s
Availability | VoID file availability check for State funding providers took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for State funding providers took 0.282085657119751s
Reputation | Calculation of the PageRank for State funding providers took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for State funding providers took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for State funding providers took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.673004150390625e-05s
Believability | Calculation of trust value for State funding providers took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 4.756321907043457s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.12045431137084961s
Availability | VoID file availability check for Organizations active in R&D took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2988319396972656s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.910064697265625e-05s
Believability | Calculation of trust value for Organizations active in R&D took 4.291534423828125e-06s
INFO | --- Analysis for cz-vavai-organizations took 5.014057874679565s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.12080955505371094s
Availability | VoID file availability check for R&D Programmes took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.2980988025665283s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020267009735107422s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.267692565917969e-05s
Believability | Calculation of trust value for R&D Programmes took 9.5367431640625e-06s
INFO | --- Analysis for cz-vavai-programmes took 3.118328094482422s
Availability | SPARQL endpoint availability check for R&D Projects took 0.11957025527954102s
Availability | VoID file availability check for R&D Projects took 0.0007157325744628906s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.29741454124450684s
Reputation | Calculation of the PageRank for R&D Projects took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.124641418457031e-05s
Believability | Calculation of trust value for R&D Projects took 5.0067901611328125e-06s
INFO | --- Analysis for cz-vavai-projects took 3.0944769382476807s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.11972403526306152s
Availability | VoID file availability check for Institutional research plans took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2813529968261719s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020117998123168945s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.910064697265625e-05s
Believability | Calculation of trust value for Institutional research plans took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-research-plans took 3.0294339656829834s
Availability | SPARQL endpoint availability check for Results of R&D took 0.12027621269226074s
Availability | VoID file availability check for Results of R&D took 0.0007390975952148438s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2728416919708252s
Reputation | Calculation of the PageRank for Results of R&D took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.00543212890625e-05s
Believability | Calculation of trust value for Results of R&D took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-results took 2.9725704193115234s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.13018107414245605s
Availability | VoID file availability check for Tenders in R&D took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.29567384719848633s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.020213842391967773s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.267692565917969e-05s
Believability | Calculation of trust value for Tenders in R&D took 4.76837158203125e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.9770777225494385s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.3392181396484375e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2773454189300537s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.4809112548828125e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 5.9604644775390625e-06s
INFO | --- Analysis for czech_addresses took 4.680901288986206s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.560711145401001s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.29787635803222656s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020216941833496094s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 5.9604644775390625e-06s
INFO | --- Analysis for DanteLatinLoanwords took 4.393849849700928s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.5134596824645996s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0006096363067626953s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 140.94628858566284s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.124413013458252s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 1.6113197803497314s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 3.0268678665161133s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.3363778591156s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.2664501667022705s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.13317227363586426s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.38175225257873535s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.3575098514556885s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2599203586578369s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.26177978515625s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 78.57714867591858s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.24993491172790527s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.0495514869689941s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.5096879005432129s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.24977922439575195s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.25490283966064453s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.24695873260498047s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.8224356174469s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.796287536621094e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.2488856315612793s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.5526823997497559s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.47313594818115234s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.6467392444610596s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.30354738235473633s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 1.7572259902954102s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 1.4201433658599854s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 86.46005392074585s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2540879249572754s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.5119411945343018s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.5034377574920654s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 42.77949905395508s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.2457594871520996s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.636470079421997s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.5880281925201416s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 12.792099952697754s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.654111623764038s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 43.56195688247681s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.3238012790679932s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 13.924748420715332s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8619277477264404s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.26168084144592285s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.38011956214904785s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 3.8520963191986084s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.5098860263824463s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021498680114746094s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00014019012451171875s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 1.6689300537109375e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 7.3909759521484375e-06s
INFO | --- Analysis for data-bnf-fr took 760.1151382923126s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.24958419799804688s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005471706390380859s
Extra | Recovery of all triples for Open Data from the Italian National Research Council took 1.0752580165863037s
Performance | Total latancy measurement for Open Data from the Italian National Research Council took 0.5838515758514404s
Amount of data | Number of triples check for Open Data from the Italian National Research Council took 8.117307186126709s
Interoperability | New terms check for Open Data from the Italian National Research Council took 2.384782314300537s
Versatility | Languages check for Open Data from the Italian National Research Council took 0.16695094108581543s
Interpretability | Number of blank nodes check for Open Data from the Italian National Research Council took 0.6492936611175537s
Security | Check HTTPS for Open Data from the Italian National Research Council took 0.06970071792602539s
Interpretability | RDF structures check for Open Data from the Italian National Research Council took 0.15941429138183594s
Versatility | Serialization formats check for Open Data from the Italian National Research Council took 0.16227030754089355s
Availability | RDF dump link check for Open Data from the Italian National Research Council took 0.14259624481201172s
License | MR license check for Open Data from the Italian National Research Council took 0.15763545036315918s
License | HR license check for Open Data from the Italian National Research Council took 11.992324352264404s
Amount of data | Number of property check for Open Data from the Italian National Research Council took 0.15375185012817383s
Understandability | Number of label check for Open Data from the Italian National Research Council took 3.9296815395355225s
Understandability | URI regex check for Open Data from the Italian National Research Council took 0.2879784107208252s
Understandability | Vocabs check for Open Data from the Italian National Research Council took 0.16755890846252441s
Verifiability | Authors check for Open Data from the Italian National Research Council took 0.18756699562072754s
Verifiability | Publishers check for Open Data from the Italian National Research Council took 0.14478659629821777s
Performance | Throughput check for Open Data from the Italian National Research Council took 10.503548383712769s
Amount of data | Check the number of entities for Open Data from the Italian National Research Council took 7.05718994140625e-05s
Verifiability | Contribs. check for Open Data from the Italian National Research Council took 0.14082884788513184s
Interlinking | sameAs chians check for Open Data from the Italian National Research Council took 0.14577460289001465s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.14409422874450684s
Interlinking | skos check for Open Data from the Italian National Research Council took 0.11454010009765625s
Timeliness | dataset update frequency check for Open Data from the Italian National Research Council took 0.16651129722595215s
Currency | Creation date check for Open Data from the Italian National Research Council took 0.33719611167907715s
Currency | Modification date check for Open Data from the Italian National Research Council took 0.2984893321990967s
Rep.Conc. | URIs length for Open Data from the Italian National Research Council took 13.072057485580444s
Consistency | Deprecated classes/propertiers check for Open Data from the Italian National Research Council took 0.1439201831817627s
Accuracy | Check Functional Property for Open Data from the Italian National Research Council took 0.14313697814941406s
Accuracy | Check Inverse Functional Property for Open Data from the Italian National Research Council took 0.14453887939453125s
Accuracy | Check Empty annotation labels for Open Data from the Italian National Research Council took 0.6440534591674805s
Accuracy | Check White space in annotation for Open Data from the Italian National Research Council took 0.03230714797973633s
Accuracy | Check Datatype consistency for Open Data from the Italian National Research Council took 0.02843499183654785s
Consistency | Disjoint class check for Open Data from the Italian National Research Council took 0.14859795570373535s
Consistency | Check Misplaced properties for Open Data from the Italian National Research Council took 10.569897174835205s
Consistency | Misplaced classes for Open Data from the Italian National Research Council took 0.2741386890411377s
Consistency | Check Ontology hijacking for Open Data from the Italian National Research Council took 1.8146235942840576s
Consistency | Check Invalid usage of undefined classes for Open Data from the Italian National Research Council took 1.215177297592163s
Consistency | Check Invalid usage of undefined properties for Open Data from the Italian National Research Council took 12.158396244049072s
Conciseness | Check Extensional conciseness for Open Data from the Italian National Research Council took 0.03277850151062012s
Conciseness | Check Intensional conciseness for Open Data from the Italian National Research Council took 0.21931743621826172s
Security | Sign check for Open Data from the Italian National Research Council took 0.14194178581237793s
Availability | Check URIs Dereferenciability for Open Data from the Italian National Research Council took 833.9462072849274s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 1.060551404953003s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.021298646926879883s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 8.130073547363281e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.7220458984375e-06s
INFO | --- Analysis for data-cnr-it took 969.7482643127441s
Availability | SPARQL endpoint availability check for Data.gov took 1.7705035209655762s
Availability | VoID file availability check for Data.gov took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for Data.gov took 0.27993321418762207s
Reputation | Calculation of the PageRank for Data.gov took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for Data.gov took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Data.gov took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.170967102050781e-05s
Believability | Calculation of trust value for Data.gov took 5.4836273193359375e-06s
INFO | --- Analysis for data-gov took 19.83056664466858s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.1208956241607666s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.30339932441711426s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.628036499023438e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 5.9604644775390625e-06s
INFO | --- Analysis for data-gov-ie took 3.4017558097839355s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.76837158203125e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.27785825729370117s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02014756202697754s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 7.271766662597656e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 5.245208740234375e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 3.5447449684143066s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.59857964515686s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.000728607177734375s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.29753804206848145s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007214546203613281s
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 159.85299682617188s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.16183137893676758s
Availability | VoID file availability check for Climb Dataincubator took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.2781960964202881s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0008037090301513672s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 8.225440979003906e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-climb took 2.8289215564727783s
Availability | SPARQL endpoint availability check for Discogs in RDF took 6.604194641113281e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.2774467468261719s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.202957153320312e-05s
Believability | Calculation of trust value for Discogs in RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-discogs took 6.711050271987915s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.06290578842163086s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.2962074279785156s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.1975250244140625e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 4.76837158203125e-06s
INFO | --- Analysis for data-incubator-metoffice took 5.473981142044067s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.060243844985961914s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.2929713726043701s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020295381546020508s
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.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.678436279296875e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 6.198883056640625e-06s
INFO | --- Analysis for data-incubator-moseley took 7.919483661651611s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.06357002258300781s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2978060245513916s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.02025628089904785s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 8.463859558105469e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.7325949668884277s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 9.059464931488037s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.289233922958374s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.869171142578125e-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 16.13516092300415s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.08258509635925293s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2909548282623291s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020327329635620117s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.534027099609375e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 7.3909759521484375e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.654475212097168s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.060204505920410156s
Availability | VoID file availability check for Pokedex data in RDF took 0.0003211498260498047s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.29613709449768066s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.012222290039062e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-pokedex took 4.418181419372559s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.07805848121643066s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0004215240478515625s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.27887868881225586s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.749961853027344e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.6788012981414795s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 30.15248966217041s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0006952285766601562s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.2828824520111084s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.866455078125e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 6.4373016357421875e-06s
INFO | --- Analysis for data-open-ac-uk took 103.50336623191833s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.937037467956543s
Availability | VoID file availability check for Persée in RDF took 0.0007004737854003906s
Extra | Recovery of all triples for Persée in RDF took 2.879570484161377s
Performance | Total latancy measurement for Persée in RDF took 0.7972495555877686s
Amount of data | Number of triples check for Persée in RDF took 12.494392395019531s
Interoperability | New terms check for Persée in RDF took 1.7720541954040527s
Versatility | Languages check for Persée in RDF took 121.07841730117798s
Interpretability | Number of blank nodes check for Persée in RDF took 0.6096851825714111s
Interpretability | RDF structures check for Persée in RDF took 0.6532058715820312s
Versatility | Serialization formats check for Persée in RDF took 0.8350830078125s
Availability | RDF dump link check for Persée in RDF took 0.29088497161865234s
License | MR license check for Persée in RDF took 1.1964964866638184s
License | HR license check for Persée in RDF took 38.43878149986267s
Amount of data | Number of property check for Persée in RDF took 0.2062978744506836s
Understandability | Number of label check for Persée in RDF took 2.138392210006714s
Understandability | URI regex check for Persée in RDF took 0.8200640678405762s
Understandability | Vocabs check for Persée in RDF took 0.30492711067199707s
Verifiability | Authors check for Persée in RDF took 0.160048246383667s
Verifiability | Publishers check for Persée in RDF took 0.14748597145080566s
Performance | Throughput check for Persée in RDF took 10.440558195114136s
Amount of data | Check the number of entities for Persée in RDF took 7.319450378417969e-05s
Verifiability | Contribs. check for Persée in RDF took 0.15142321586608887s
Interlinking | sameAs chians check for Persée in RDF took 0.2399137020111084s
Interlinking | skos check for Persée in RDF took 0.6576273441314697s
Interlinking | skos check for Persée in RDF took 0.17448067665100098s
Timeliness | dataset update frequency check for Persée in RDF took 0.6724536418914795s
Currency | Creation date check for Persée in RDF took 0.541419267654419s
Currency | Modification date check for Persée in RDF took 0.29852843284606934s
Rep.Conc. | URIs length for Persée in RDF took 4.062048435211182s
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.17075109481811523s
Accuracy | Check Functional Property for Persée in RDF took 0.15919184684753418s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.15784740447998047s
Accuracy | Check Empty annotation labels for Persée in RDF took 1.0510618686676025s
Accuracy | Check White space in annotation for Persée in RDF took 0.037397146224975586s
Accuracy | Check Datatype consistency for Persée in RDF took 0.028908491134643555s
Consistency | Disjoint class check for Persée in RDF took 0.29573869705200195s
Consistency | Check Misplaced properties for Persée in RDF took 2.660505771636963s
Consistency | Misplaced classes for Persée in RDF took 0.24472332000732422s
Consistency | Check Ontology hijacking for Persée in RDF took 1.9089059829711914s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.1828398704528809s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.7050294876098633s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.03518342971801758s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.15163302421569824s
Security | Sign check for Persée in RDF took 0.833284854888916s
Availability | Check URIs Dereferenciability for Persée in RDF took 1519.2647421360016s
Completeness | Calculation of interlinking completeness for Persée in RDF took 131.93244409561157s
Reputation | Calculation of the PageRank for Persée in RDF took 0.022424936294555664s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0011794567108154297s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.0001499652862548828s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Persée in RDF took 1.430511474609375e-05s
INFO | --- Analysis for data-persee-fr took 2169.239743947983s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 9.751319885253906e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00066375732421875s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 131.07033681869507s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.021374940872192383s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.123283386230469e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 1.8596649169921875e-05s
INFO | --- Analysis for data-southampton-ac-uk took 1049.0429162979126s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 20.378088235855103s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 132.032705783844s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020596742630004883s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.0001227855682373047s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.5735626220703125e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 909.2730021476746s
Availability | SPARQL endpoint availability check for Open Data Web took 0.24204063415527344s
Availability | VoID file availability check for Open Data Web took 0.0007054805755615234s
Completeness | Calculation of interlinking completeness for Open Data Web took 131.0730230808258s
Reputation | Calculation of the PageRank for Open Data Web took 0.021181106567382812s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0008454322814941406s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 7.033348083496094e-05s
Believability | Calculation of trust value for Open Data Web took 1.5020370483398438e-05s
INFO | --- Analysis for data.odw.tw took 786.9201481342316s
Availability | SPARQL endpoint availability check for DataFAQs took 9.489059448242188e-05s
Availability | VoID file availability check for DataFAQs took 0.0006971359252929688s
Completeness | Calculation of interlinking completeness for DataFAQs took 131.0705213546753s
Reputation | Calculation of the PageRank for DataFAQs took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.7670135498046875e-05s
Believability | Calculation of trust value for DataFAQs took 1.0728836059570312e-05s
INFO | --- Analysis for datafaqs took 1047.2462203502655s
Availability | SPARQL endpoint availability check for datahub took 0.00010585784912109375s
Availability | VoID file availability check for datahub took 0.0008444786071777344s
Completeness | Calculation of interlinking completeness for datahub took 130.2769558429718s
Reputation | Calculation of the PageRank for datahub took 0.021030664443969727s
Interlinking | Calculation of Degree of Connection for datahub took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for datahub took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for datahub took 6.914138793945312e-05s
Believability | Calculation of trust value for datahub took 1.5497207641601562e-05s
INFO | --- Analysis for datahub took 786.5207920074463s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 6.135304689407349s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.724132776260376s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020449399948120117s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.910064697265625e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 6.9141387939453125e-06s
INFO | --- Analysis for datahub-kr-datamap took 410.1568007469177s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.32334136962890625s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.6646780967712402s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02028656005859375s
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.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.843971252441406e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.4373016357421875e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.404587745666504s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.317344188690186s
Availability | VoID file availability check for datos-artium-org took 0.0006792545318603516s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.24051809310913086s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020819902420043945s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012636184692382812s
Believability | Calculation of trust value for datos-artium-org took 6.9141387939453125e-06s
INFO | --- Analysis for datos-artium-org took 165.52234649658203s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 2.359297513961792s
Availability | VoID file availability check for Datos.bcn.cl took 0.00061798095703125s
Extra | Recovery of all triples for Datos.bcn.cl took 59.89354181289673s
Performance | Total latancy measurement for Datos.bcn.cl took 5.845123291015625s
Amount of data | Number of triples check for Datos.bcn.cl took 14.86122441291809s
Interoperability | New terms check for Datos.bcn.cl took 3.4554665088653564s
Versatility | Languages check for Datos.bcn.cl took 301.0315179824829s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.3197507858276367s
Security | Check HTTPS for Datos.bcn.cl took 0.7256002426147461s
Interpretability | RDF structures check for Datos.bcn.cl took 1.4015955924987793s
Versatility | Serialization formats check for Datos.bcn.cl took 1.2851450443267822s
Availability | RDF dump link check for Datos.bcn.cl took 1.1682965755462646s
License | MR license check for Datos.bcn.cl took 1.1814403533935547s
License | HR license check for Datos.bcn.cl took 56.565858125686646s
Amount of data | Number of property check for Datos.bcn.cl took 1.1843245029449463s
Understandability | Number of label check for Datos.bcn.cl took 2.21113920211792s
Understandability | URI regex check for Datos.bcn.cl took 2.336287498474121s
Understandability | Vocabs check for Datos.bcn.cl took 1.1694316864013672s
Verifiability | Authors check for Datos.bcn.cl took 1.217864990234375s
Verifiability | Publishers check for Datos.bcn.cl took 1.1691200733184814s
Performance | Throughput check for Datos.bcn.cl took 11.663291931152344s
Amount of data | Check the number of entities for Datos.bcn.cl took 8.702278137207031e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 1.1680448055267334s
Interlinking | sameAs chians check for Datos.bcn.cl took 1.188066005706787s
Interlinking | skos check for Datos.bcn.cl took 1.1740121841430664s
Interlinking | skos check for Datos.bcn.cl took 1.1697585582733154s
Timeliness | dataset update frequency check for Datos.bcn.cl took 1.184220314025879s
Currency | Creation date check for Datos.bcn.cl took 2.3510396480560303s
Currency | Modification date check for Datos.bcn.cl took 1.174985408782959s
Rep.Conc. | URIs length for Datos.bcn.cl took 59.19744062423706s
Interoperability | New vocabularies check for Datos.bcn.cl took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 1.1720774173736572s
Accuracy | Check Functional Property for Datos.bcn.cl took 1.172165870666504s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 1.1929728984832764s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 20.73068356513977s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.2477586269378662s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.28006458282470703s
Consistency | Disjoint class check for Datos.bcn.cl took 1.179957628250122s
Consistency | Check Misplaced properties for Datos.bcn.cl took 5.990412473678589s
Consistency | Misplaced classes for Datos.bcn.cl took 2.043273687362671s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 29.64195728302002s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.2317848205566406s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 5.82537579536438s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.299771785736084s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 1.398021936416626s
Security | Sign check for Datos.bcn.cl took 1.1788475513458252s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 8709.001159667969s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.4803810119628906s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 9.703636169433594e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.6689300537109375e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 1.0251998901367188e-05s
INFO | --- Analysis for datos-bcn-cl took 9623.93747639656s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.40641260147094727s
Availability | VoID file availability check for datos.bne.es took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.6823599338531494s
Reputation | Calculation of the PageRank for datos.bne.es took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011873245239257812s
Believability | Calculation of trust value for datos.bne.es took 8.106231689453125e-06s
INFO | --- Analysis for datos-bne-es took 5.9495320320129395s
Availability | SPARQL endpoint availability check for dbacademic took 0.1697690486907959s
Availability | VoID file availability check for dbacademic took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for dbacademic took 0.23676443099975586s
Reputation | Calculation of the PageRank for dbacademic took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.123283386230469e-05s
Believability | Calculation of trust value for dbacademic took 8.821487426757812e-06s
INFO | --- Analysis for dbacademic took 3.1890296936035156s
Availability | SPARQL endpoint availability check for DBkWik took 0.19783854484558105s
Availability | VoID file availability check for DBkWik took 0.0006327629089355469s
Extra | Recovery of all triples for DBkWik took 2.8291244506835938s
Performance | Total latancy measurement for DBkWik took 0.4970417022705078s
Amount of data | Number of triples check for DBkWik took 10.604061603546143s
Interoperability | New terms check for DBkWik took 2.1152565479278564s
Versatility | Languages check for DBkWik took 60.5658118724823s
Interpretability | Number of blank nodes check for DBkWik took 0.11809301376342773s
Interpretability | RDF structures check for DBkWik took 0.19047141075134277s
Versatility | Serialization formats check for DBkWik took 0.3091263771057129s
Availability | RDF dump link check for DBkWik took 2.8387110233306885s
License | MR license check for DBkWik took 0.5157284736633301s
License | HR license check for DBkWik took 60.986329317092896s
Amount of data | Number of property check for DBkWik took 0.13024258613586426s
Understandability | Number of label check for DBkWik took 1.775301218032837s
Understandability | URI regex check for DBkWik took 0.2810056209564209s
Understandability | Vocabs check for DBkWik took 0.11968064308166504s
Verifiability | Authors check for DBkWik took 0.12726116180419922s
Verifiability | Publishers check for DBkWik took 0.09834074974060059s
Performance | Throughput check for DBkWik took 10.226591110229492s
Amount of data | Check the number of entities for DBkWik took 7.414817810058594e-05s
Verifiability | Contribs. check for DBkWik took 0.1177973747253418s
Interlinking | sameAs chians check for DBkWik took 0.32531237602233887s
Interlinking | skos check for DBkWik took 0.42792773246765137s
Interlinking | skos check for DBkWik took 0.09569478034973145s
Timeliness | dataset update frequency check for DBkWik took 0.1837761402130127s
Currency | Creation date check for DBkWik took 0.3940122127532959s
Currency | Modification date check for DBkWik took 0.2222304344177246s
Rep.Conc. | URIs length for DBkWik took 11.732900381088257s
Consistency | Deprecated classes/propertiers check for DBkWik took 0.11436843872070312s
Accuracy | Check Functional Property for DBkWik took 0.24585986137390137s
Accuracy | Check Inverse Functional Property for DBkWik took 0.27604126930236816s
Accuracy | Check Empty annotation labels for DBkWik took 1.6304879188537598s
Accuracy | Check White space in annotation for DBkWik took 0.023999929428100586s
Accuracy | Check Datatype consistency for DBkWik took 0.027763843536376953s
Consistency | Disjoint class check for DBkWik took 0.1373734474182129s
Consistency | Check Misplaced properties for DBkWik took 12.572032690048218s
Consistency | Misplaced classes for DBkWik took 0.7139427661895752s
Consistency | Check Ontology hijacking for DBkWik took 1.8620684146881104s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.1364035606384277s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.779770135879517s
Conciseness | Check Extensional conciseness for DBkWik took 0.032379150390625s
Conciseness | Check Intensional conciseness for DBkWik took 1.4460117816925049s
Security | Sign check for DBkWik took 0.23831725120544434s
Availability | Check URIs Dereferenciability for DBkWik took 11.444538593292236s
Completeness | Calculation of interlinking completeness for DBkWik took 0.7170407772064209s
Reputation | Calculation of the PageRank for DBkWik took 0.02179121971130371s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for DBkWik took 7.486343383789062e-05s
Believability | Calculation of trust value for DBkWik took 6.67572021484375e-06s
INFO | --- Analysis for dbkwik took 1457.802588224411s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.220008850097656e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.7434611320495605s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02028679847717285s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00012540817260742188s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 1.239776611328125e-05s
INFO | --- Analysis for dblp-deusto-gnoss took 45.7564640045166s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.30060744285583496s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005390644073486328s
Extra | Recovery of all triples for dblp Knowledge Graph took 57.56729531288147s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7091467380523682s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.12227702140808105s
Interoperability | New terms check for dblp Knowledge Graph took 1.7328062057495117s
Versatility | Languages check for dblp Knowledge Graph took 30.272254943847656s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.1459007263183594s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.15623021125793457s
Versatility | Serialization formats check for dblp Knowledge Graph took 1.1700308322906494s
Availability | RDF dump link check for dblp Knowledge Graph took 0.13163137435913086s
License | MR license check for dblp Knowledge Graph took 0.1448042392730713s
License | HR license check for dblp Knowledge Graph took 30.133759260177612s
Amount of data | Number of property check for dblp Knowledge Graph took 0.5264017581939697s
Understandability | Number of label check for dblp Knowledge Graph took 1.5401675701141357s
Understandability | URI regex check for dblp Knowledge Graph took 1.4311611652374268s
Understandability | Vocabs check for dblp Knowledge Graph took 0.42957568168640137s
Verifiability | Authors check for dblp Knowledge Graph took 0.15517592430114746s
Verifiability | Publishers check for dblp Knowledge Graph took 0.14213013648986816s
Performance | Throughput check for dblp Knowledge Graph took 10.899962186813354s
Amount of data | Check the number of entities for dblp Knowledge Graph took 8.344650268554688e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.14910674095153809s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.1933910846710205s
Interlinking | skos check for dblp Knowledge Graph took 0.13178730010986328s
Interlinking | skos check for dblp Knowledge Graph took 0.13001680374145508s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.14342069625854492s
Currency | Creation date check for dblp Knowledge Graph took 0.27915024757385254s
Currency | Modification date check for dblp Knowledge Graph took 0.2758452892303467s
Rep.Conc. | URIs length for dblp Knowledge Graph took 27.90326166152954s
Interoperability | New vocabularies check for dblp Knowledge Graph took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.13442754745483398s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.12364339828491211s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.12734675407409668s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 17.179073333740234s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.092505931854248s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.319754600524902s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.12968087196350098s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.2630622386932373s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 19.549372911453247s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 16599.80684351921s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 4.097652196884155s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.6987998485565186s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.15018749237060547s
Security | Sign check for dblp Knowledge Graph took 0.1359238624572754s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 2.2194831371307373s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 1.6007945537567139s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 3.5762786865234375e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 2.6226043701171875e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 8.344650268554688e-06s
INFO | --- Analysis for dblp-kg took 16890.863507032394s
Availability | SPARQL endpoint availability check for dbnary took 0.2492058277130127s
Availability | VoID file availability check for dbnary took 0.0005159378051757812s
Extra | Recovery of all triples for dbnary took 1.6722476482391357s
Performance | Total latancy measurement for dbnary took 0.32998061180114746s
Amount of data | Number of triples check for dbnary took 1.3270769119262695s
Interoperability | New terms check for dbnary took 3.650310754776001s
Versatility | Languages check for dbnary took 60.92518210411072s
Interpretability | Number of blank nodes check for dbnary took 4.174103498458862s
Security | Check HTTPS for dbnary took 0.18741726875305176s
Interpretability | RDF structures check for dbnary took 0.1636214256286621s
Versatility | Serialization formats check for dbnary took 0.27472710609436035s
Availability | RDF dump link check for dbnary took 0.0597834587097168s
License | MR license check for dbnary took 0.26680707931518555s
License | HR license check for dbnary took 60.04750370979309s
Amount of data | Number of property check for dbnary took 0.0950918197631836s
Understandability | Number of label check for dbnary took 0.775653600692749s
Understandability | URI regex check for dbnary took 0.1252436637878418s
Understandability | Vocabs check for dbnary took 0.2476956844329834s
Verifiability | Authors check for dbnary took 0.4444737434387207s
Verifiability | Publishers check for dbnary took 0.12284088134765625s
Performance | Throughput check for dbnary took 10.384460926055908s
Amount of data | Check the number of entities for dbnary took 0.00011301040649414062s
Verifiability | Contribs. check for dbnary took 0.11981034278869629s
Interlinking | sameAs chians check for dbnary took 0.09101700782775879s
Interlinking | skos check for dbnary took 0.24060511589050293s
Interlinking | skos check for dbnary took 0.0989072322845459s
Timeliness | dataset update frequency check for dbnary took 0.15511035919189453s
Currency | Creation date check for dbnary took 0.21079730987548828s
Currency | Modification date check for dbnary took 0.18254566192626953s
Rep.Conc. | URIs length for dbnary took 11.582461595535278s
Interoperability | New vocabularies check for dbnary took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.08636879920959473s
Accuracy | Check Functional Property for dbnary took 0.12643861770629883s
Accuracy | Check Inverse Functional Property for dbnary took 0.10348367691040039s
Accuracy | Check Empty annotation labels for dbnary took 0.46718788146972656s
Accuracy | Check White space in annotation for dbnary took 0.02514171600341797s
Accuracy | Check Datatype consistency for dbnary took 0.028329849243164062s
Consistency | Disjoint class check for dbnary took 0.15290069580078125s
Consistency | Check Misplaced properties for dbnary took 9.090287685394287s
Consistency | Misplaced classes for dbnary took 0.21410226821899414s
Consistency | Check Ontology hijacking for dbnary took 1.7708499431610107s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.2347352504730225s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.191956520080566s
Conciseness | Check Extensional conciseness for dbnary took 0.03210306167602539s
Conciseness | Check Intensional conciseness for dbnary took 0.1636500358581543s
Security | Sign check for dbnary took 0.06502485275268555s
Availability | Check URIs Dereferenciability for dbnary took 10.412961959838867s
Completeness | Calculation of interlinking completeness for dbnary took 0.24596762657165527s
Reputation | Calculation of the PageRank for dbnary took 0.021198511123657227s
Interlinking | Calculation of Degree of Connection for dbnary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for dbnary took 6.365776062011719e-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 304.54411029815674s
Availability | SPARQL endpoint availability check for DBpedia took 0.36034321784973145s
Availability | VoID file availability check for DBpedia took 0.000667572021484375s
Extra | Recovery of all triples for DBpedia took 1.5598371028900146s
Performance | Total latancy measurement for DBpedia took 1.1794068813323975s
Amount of data | Number of triples check for DBpedia took 1.4262592792510986s
Interoperability | New terms check for DBpedia took 5.699315547943115s
Versatility | Languages check for DBpedia took 31.185648441314697s
Interpretability | Number of blank nodes check for DBpedia took 0.1668550968170166s
Security | Check HTTPS for DBpedia took 0.10204958915710449s
Interpretability | RDF structures check for DBpedia took 0.18697237968444824s
Versatility | Serialization formats check for DBpedia took 0.2345271110534668s
Availability | RDF dump link check for DBpedia took 0.4087519645690918s
License | MR license check for DBpedia took 0.20402932167053223s
License | HR license check for DBpedia took 31.666277408599854s
Amount of data | Number of property check for DBpedia took 0.19320964813232422s
Understandability | Number of label check for DBpedia took 2.6311445236206055s
Understandability | URI regex check for DBpedia took 0.34024906158447266s
Understandability | Vocabs check for DBpedia took 0.5248584747314453s
Verifiability | Authors check for DBpedia took 0.36110830307006836s
Verifiability | Publishers check for DBpedia took 0.17170500755310059s
Performance | Throughput check for DBpedia took 11.041276216506958s
Amount of data | Check the number of entities for DBpedia took 7.319450378417969e-05s
Verifiability | Contribs. check for DBpedia took 0.3679697513580322s
Interlinking | sameAs chians check for DBpedia took 2.115457534790039s
Interlinking | skos check for DBpedia took 0.17740511894226074s
Interlinking | skos check for DBpedia took 0.16182398796081543s
Timeliness | dataset update frequency check for DBpedia took 0.1842637062072754s
Currency | Creation date check for DBpedia took 0.3705272674560547s
Currency | Modification date check for DBpedia took 0.36890435218811035s
Rep.Conc. | URIs length for DBpedia took 36.369081020355225s
Interoperability | New vocabularies check for DBpedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.182877779006958s
Accuracy | Check Functional Property for DBpedia took 0.26899027824401855s
Accuracy | Check Inverse Functional Property for DBpedia took 0.25689005851745605s
Accuracy | Check Empty annotation labels for DBpedia took 2.49511456489563s
Accuracy | Check White space in annotation for DBpedia took 0.030994415283203125s
Accuracy | Check Datatype consistency for DBpedia took 0.027687788009643555s
Consistency | Disjoint class check for DBpedia took 0.16680645942687988s
Consistency | Check Misplaced properties for DBpedia took 34.048180103302s
Consistency | Misplaced classes for DBpedia took 0.7494215965270996s
Consistency | Check Ontology hijacking for DBpedia took 2.7957334518432617s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.1324784755706787s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.4643170833587646s
Conciseness | Check Extensional conciseness for DBpedia took 0.03186225891113281s
Conciseness | Check Intensional conciseness for DBpedia took 2.9693703651428223s
Security | Sign check for DBpedia took 0.19336628913879395s
Availability | Check URIs Dereferenciability for DBpedia took 6910.739122390747s
Completeness | Calculation of interlinking completeness for DBpedia took 1.1635551452636719s
Reputation | Calculation of the PageRank for DBpedia took 0.02091240882873535s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008935928344726562s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.6689300537109375e-06s
Believability | Calculation of trust value for DBpedia took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia took 7252.653225183487s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0007922649383544922s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.6828300952911377s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.604194641113281e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 8.938238382339478s
Availability | SPARQL endpoint availability check for DBpedia Commons took 6.206162691116333s
Availability | VoID file availability check for DBpedia Commons took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.660975456237793s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.021128177642822266s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0010693073272705078s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 8.797645568847656e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.33514404296875e-05s
INFO | --- Analysis for dbpedia-commons took 16.25037145614624s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia in German took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.2371680736541748s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.532669067382812e-05s
Believability | Calculation of trust value for DBpedia in German took 6.4373016357421875e-06s
INFO | --- Analysis for dbpedia-de took 2.637138605117798s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.9483163356781s
Availability | VoID file availability check for DBpedia in Greek took 0.00067138671875s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.24259328842163086s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00019598007202148438s
Believability | Calculation of trust value for DBpedia in Greek took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-el took 46.82372713088989s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 0.8077065944671631s
Availability | VoID file availability check for DBpedia in Spanish took 0.0007097721099853516s
Extra | Recovery of all triples for DBpedia in Spanish took 22.790210723876953s
Performance | Total latancy measurement for DBpedia in Spanish took 13.512004852294922s
Amount of data | Number of triples check for DBpedia in Spanish took 3.396077871322632s
Interoperability | New terms check for DBpedia in Spanish took 12.7637619972229s
Versatility | Languages check for DBpedia in Spanish took 31.26296591758728s
Interpretability | Number of blank nodes check for DBpedia in Spanish took 0.422626256942749s
Security | Check HTTPS for DBpedia in Spanish took 0.1261894702911377s
Interpretability | RDF structures check for DBpedia in Spanish took 1.0758886337280273s
Versatility | Serialization formats check for DBpedia in Spanish took 0.5792076587677002s
Availability | RDF dump link check for DBpedia in Spanish took 3.0150954723358154s
License | MR license check for DBpedia in Spanish took 2.6733076572418213s
License | HR license check for DBpedia in Spanish took 32.72066783905029s
Amount of data | Number of property check for DBpedia in Spanish took 0.43846988677978516s
Understandability | Number of label check for DBpedia in Spanish took 1.348724365234375s
Understandability | URI regex check for DBpedia in Spanish took 0.9293510913848877s
Understandability | Vocabs check for DBpedia in Spanish took 2.8515632152557373s
Verifiability | Authors check for DBpedia in Spanish took 3.196978807449341s
Verifiability | Publishers check for DBpedia in Spanish took 2.744422197341919s
Performance | Throughput check for DBpedia in Spanish took 27.70363736152649s
Amount of data | Check the number of entities for DBpedia in Spanish took 7.700920104980469e-05s
Verifiability | Contribs. check for DBpedia in Spanish took 2.7281136512756348s
Interlinking | sameAs chians check for DBpedia in Spanish took 3.3916478157043457s
Interlinking | skos check for DBpedia in Spanish took 2.4677443504333496s
Interlinking | skos check for DBpedia in Spanish took 2.5300402641296387s
Timeliness | dataset update frequency check for DBpedia in Spanish took 3.279418706893921s
Currency | Creation date check for DBpedia in Spanish took 5.926646947860718s
Currency | Modification date check for DBpedia in Spanish took 4.450478792190552s
Rep.Conc. | URIs length for DBpedia in Spanish took 27.090813398361206s
Interoperability | New vocabularies check for DBpedia in Spanish took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Spanish took 1.7811737060546875s
Accuracy | Check Functional Property for DBpedia in Spanish took 4.575223445892334s
Accuracy | Check Inverse Functional Property for DBpedia in Spanish took 2.82022762298584s
Accuracy | Check Empty annotation labels for DBpedia in Spanish took 11.679625272750854s
Accuracy | Check White space in annotation for DBpedia in Spanish took 0.031133174896240234s
Accuracy | Check Datatype consistency for DBpedia in Spanish took 0.028081655502319336s
Consistency | Disjoint class check for DBpedia in Spanish took 1.7277803421020508s
Consistency | Check Misplaced properties for DBpedia in Spanish took 25.69172501564026s
Consistency | Misplaced classes for DBpedia in Spanish took 9.361331224441528s
Consistency | Check Ontology hijacking for DBpedia in Spanish took 15.578388690948486s
Consistency | Check Invalid usage of undefined classes for DBpedia in Spanish took 1.1915569305419922s
Consistency | Check Invalid usage of undefined properties for DBpedia in Spanish took 18.721203565597534s
Conciseness | Check Extensional conciseness for DBpedia in Spanish took 0.035186767578125s
Conciseness | Check Intensional conciseness for DBpedia in Spanish took 15.113531589508057s
Security | Sign check for DBpedia in Spanish took 2.7561089992523193s
Availability | Check URIs Dereferenciability for DBpedia in Spanish took 11.601804494857788s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.3342933654785156s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.0001125335693359375s
Interoperability | Check the re-using of existing vocabs for DBpedia in Spanish took 1.1920928955078125e-06s
Believability | Calculation of trust value for DBpedia in Spanish took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-es took 779.9488270282745s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.2125842571258545s
Availability | VoID file availability check for DBpedia in Basque took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.23879051208496094s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 4.1484832763671875e-05s
Believability | Calculation of trust value for DBpedia in Basque took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-eu took 7.2316975593566895s
Availability | SPARQL endpoint availability check for DBpedia in French took 0.1661055088043213s
Availability | VoID file availability check for DBpedia in French took 0.000507354736328125s
Extra | Recovery of all triples for DBpedia in French took 160.52144527435303s
Performance | Total latancy measurement for DBpedia in French took 0.3631124496459961s
Amount of data | Number of triples check for DBpedia in French took 2.3166279792785645s
Interoperability | New terms check for DBpedia in French took 2.9751455783843994s
Versatility | Languages check for DBpedia in French took 300.1032512187958s
Interpretability | Number of blank nodes check for DBpedia in French took 0.17984700202941895s
Interpretability | RDF structures check for DBpedia in French took 0.7693331241607666s
Versatility | Serialization formats check for DBpedia in French took 0.31584596633911133s
Availability | RDF dump link check for DBpedia in French took 7.141063928604126s
License | MR license check for DBpedia in French took 0.9245090484619141s
License | HR license check for DBpedia in French took 135.49098443984985s
Amount of data | Number of property check for DBpedia in French took 0.209136962890625s
Understandability | Number of label check for DBpedia in French took 3.2613532543182373s
Understandability | URI regex check for DBpedia in French took 0.20156526565551758s
Understandability | Vocabs check for DBpedia in French took 0.09557461738586426s
Verifiability | Authors check for DBpedia in French took 0.09968185424804688s
Verifiability | Publishers check for DBpedia in French took 0.09490108489990234s
Performance | Throughput check for DBpedia in French took 14.590843439102173s
Amount of data | Check the number of entities for DBpedia in French took 2.1975107192993164s
Verifiability | Contribs. check for DBpedia in French took 0.0945284366607666s
Interlinking | sameAs chians check for DBpedia in French took 0.6248822212219238s
Interlinking | skos check for DBpedia in French took 0.37911510467529297s
Interlinking | skos check for DBpedia in French took 0.06876325607299805s
Timeliness | dataset update frequency check for DBpedia in French took 0.5672776699066162s
Currency | Creation date check for DBpedia in French took 0.17383480072021484s
Currency | Modification date check for DBpedia in French took 0.16603589057922363s
Rep.Conc. | URIs length for DBpedia in French took 63.43097543716431s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 0.1063389778137207s
Accuracy | Check Functional Property for DBpedia in French took 0.1399519443511963s
Accuracy | Check Inverse Functional Property for DBpedia in French took 0.11429190635681152s
Accuracy | Check Empty annotation labels for DBpedia in French took 47.52516794204712s
Accuracy | Check White space in annotation for DBpedia in French took 3.0905847549438477s
Accuracy | Check Datatype consistency for DBpedia in French took 2.6694107055664062s
Consistency | Disjoint class check for DBpedia in French took 0.09602880477905273s
Consistency | Check Misplaced properties for DBpedia in French took 8.64962911605835s
Consistency | Misplaced classes for DBpedia in French took 9.786823511123657s
Consistency | Check Ontology hijacking for DBpedia in French took 53.56860303878784s
Consistency | Check Invalid usage of undefined classes for DBpedia in French took 1.2950525283813477s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 8.238342523574829s
Conciseness | Check Extensional conciseness for DBpedia in French took 3.0356345176696777s
Conciseness | Check Intensional conciseness for DBpedia in French took 3.1215202808380127s
Security | Sign check for DBpedia in French took 0.12178969383239746s
Availability | Check URIs Dereferenciability for DBpedia in French took 880.0874381065369s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.35140061378479s
Reputation | Calculation of the PageRank for DBpedia in French took 0.0213162899017334s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 0.00010895729064941406s
Believability | Calculation of trust value for DBpedia in French took 5.9604644775390625e-06s
INFO | --- Analysis for dbpedia-fr took 1911.1161620616913s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 1.936305284500122s
Availability | VoID file availability check for DBpedia in Japanese took 4.036635875701904s
Extra | Recovery of all triples for DBpedia in Japanese took 8.671468734741211s
Performance | Total latancy measurement for DBpedia in Japanese took 6.563412189483643s
Amount of data | Number of triples check for DBpedia in Japanese took 28.49544668197632s
Interoperability | New terms check for DBpedia in Japanese took 17.23226022720337s
Versatility | Languages check for DBpedia in Japanese took 1.3112518787384033s
Interpretability | Number of blank nodes check for DBpedia in Japanese took 1.313223123550415s
Security | Check HTTPS for DBpedia in Japanese took 0.7895510196685791s
Interpretability | RDF structures check for DBpedia in Japanese took 1.3641166687011719s
Versatility | Serialization formats check for DBpedia in Japanese took 1.7063100337982178s
Availability | RDF dump link check for DBpedia in Japanese took 1.317375659942627s
License | MR license check for DBpedia in Japanese took 2.012392044067383s
License | HR license check for DBpedia in Japanese took 121.32004737854004s
Amount of data | Number of property check for DBpedia in Japanese took 1.3208591938018799s
Understandability | Number of label check for DBpedia in Japanese took 8.094537019729614s
Understandability | URI regex check for DBpedia in Japanese took 2.891852378845215s
Understandability | Vocabs check for DBpedia in Japanese took 1.4528167247772217s
Verifiability | Authors check for DBpedia in Japanese took 1.3281655311584473s
Verifiability | Publishers check for DBpedia in Japanese took 1.315892219543457s
Performance | Throughput check for DBpedia in Japanese took 13.129343271255493s
Amount of data | Check the number of entities for DBpedia in Japanese took 3.361701965332031e-05s
Verifiability | Contribs. check for DBpedia in Japanese took 1.4924299716949463s
Interlinking | sameAs chians check for DBpedia in Japanese took 2.3269832134246826s
Interlinking | skos check for DBpedia in Japanese took 1.3170857429504395s
Interlinking | skos check for DBpedia in Japanese took 1.3162047863006592s
Timeliness | dataset update frequency check for DBpedia in Japanese took 1.329699993133545s
Currency | Creation date check for DBpedia in Japanese took 2.826388120651245s
Currency | Modification date check for DBpedia in Japanese took 2.6317479610443115s
Rep.Conc. | URIs length for DBpedia in Japanese took 139.82062935829163s
Interoperability | New vocabularies check for DBpedia in Japanese took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia in Japanese took 1.33673095703125s
Accuracy | Check Functional Property for DBpedia in Japanese took 1.3405582904815674s
Accuracy | Check Inverse Functional Property for DBpedia in Japanese took 1.3366668224334717s
Accuracy | Check Empty annotation labels for DBpedia in Japanese took 4.432354688644409s
Accuracy | Check White space in annotation for DBpedia in Japanese took 0.02661442756652832s
Accuracy | Check Datatype consistency for DBpedia in Japanese took 0.029001712799072266s
Consistency | Disjoint class check for DBpedia in Japanese took 1.4310784339904785s
Consistency | Check Misplaced properties for DBpedia in Japanese took 122.62349057197571s
Consistency | Misplaced classes for DBpedia in Japanese took 3.65983510017395s
Consistency | Check Ontology hijacking for DBpedia in Japanese took 4.791178226470947s
Consistency | Check Invalid usage of undefined classes for DBpedia in Japanese took 1.2375059127807617s
Consistency | Check Invalid usage of undefined properties for DBpedia in Japanese took 122.58605551719666s
Conciseness | Check Extensional conciseness for DBpedia in Japanese took 0.033208370208740234s
Conciseness | Check Intensional conciseness for DBpedia in Japanese took 5.05832839012146s
Security | Sign check for DBpedia in Japanese took 1.3193559646606445s
Availability | Check URIs Dereferenciability for DBpedia in Japanese took 9.91493558883667s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.5470266342163086s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.02093362808227539s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.00010251998901367188s
Interoperability | Check the re-using of existing vocabs for DBpedia in Japanese took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia in Japanese took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-ja took 1168.0979237556458s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.2438507080078125e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.23258423805236816s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010061264038085938s
Believability | Calculation of trust value for dbpedia lite took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-lite took 23.02033042907715s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.1961669921875e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.6831192970275879s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.361701965332031e-05s
Believability | Calculation of trust value for DBpedia-Live took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-live took 3.985278844833374s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.25647974014282227s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2382352352142334s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.02083730697631836s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016736984252929688s
Believability | Calculation of trust value for DBpedia in Dutch took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-nl took 2.9592206478118896s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 30.213201999664307s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006577968597412109s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.23783159255981445s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.0108642578125e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 1.0728836059570312e-05s
INFO | --- Analysis for dbpedia-pt took 72.58975768089294s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.8160552978515625e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.24091243743896484s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.123283386230469e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-spotlight took 3.082455635070801s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.291534423828125e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.24358153343200684s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020396709442138672s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 8.177757263183594e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.602986812591553s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.100799560546875e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.000244140625s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.2398383617401123s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 2.9087066650390625e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.1444091796875e-05s
INFO | --- Analysis for dbpedia-wikidata took 3.520495891571045s
Availability | SPARQL endpoint availability check for DBpedia took 4.4345855712890625e-05s
Availability | VoID file availability check for DBpedia took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for DBpedia took 0.23956918716430664s
Reputation | Calculation of the PageRank for DBpedia took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for DBpedia took 3.266334533691406e-05s
Believability | Calculation of trust value for DBpedia took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia_ took 2.6673920154571533s
Availability | SPARQL endpoint availability check for DBTropes took 4.410743713378906e-05s
Availability | VoID file availability check for DBTropes took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for DBTropes took 0.24290823936462402s
Reputation | Calculation of the PageRank for DBTropes took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.560585021972656e-05s
Believability | Calculation of trust value for DBTropes took 1.2636184692382812e-05s
INFO | --- Analysis for dbtropes took 2.7289958000183105s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.315376281738281e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.24033689498901367s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 4.315376281738281e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 8.58306884765625e-06s
INFO | --- Analysis for dbtune took 2.628812789916992s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 6.866455078125e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006399154663085938s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.24356675148010254s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02094411849975586s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.7697296142578125e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 8.58306884765625e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.336199522018433s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 8.96453857421875e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.2420516014099121s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02023935317993164s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007505416870117188s
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 6.67572021484375e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.979764938354492s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 7.078510522842407s
Availability | VoID file availability check for DBTune.org/classical took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.24494028091430664s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.462501525878906e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-classical took 22.580625295639038s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.411490201950073s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2400956153869629s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020452022552490234s
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.00072479248046875s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.985664367675781e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 1.239776611328125e-05s
INFO | --- Analysis for dbtune-john-peel-sessions took 28.632314682006836s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.413881063461304s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.23912835121154785s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.67572021484375e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-magnatune took 23.923516511917114s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.420169115066528s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2524285316467285s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011134147644042969s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 5.9604644775390625e-06s
INFO | --- Analysis for dbtune-musicbrainz took 23.923112392425537s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.367426872253418s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.24051260948181152s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.14984130859375e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-myspace took 17.864168405532837s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.220008850097656e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.000244140625s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2460322380065918s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.152557373046875e-06s
INFO | --- Analysis for dclg-openuplabs took 2.646982192993164s
Availability | SPARQL endpoint availability check for data.dcs took 4.363059997558594e-05s
Availability | VoID file availability check for data.dcs took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for data.dcs took 0.24332571029663086s
Reputation | Calculation of the PageRank for data.dcs took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.341934204101562e-05s
Believability | Calculation of trust value for data.dcs took 6.4373016357421875e-06s
INFO | --- Analysis for dcs-sheffield took 2.276092052459717s
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.0002727508544921875s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.2386767864227295s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 2.86102294921875e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 6.9141387939453125e-06s
INFO | --- Analysis for de-budget took 2.6279499530792236s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.315376281738281e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.23771214485168457s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.743171691894531e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.152557373046875e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 3.944161891937256s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.291534423828125e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.2398853302001953s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0008394718170166016s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 5.650520324707031e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.3113021850585938e-05s
INFO | --- Analysis for debian-package-tracking-system took 4.295443773269653s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 4.7206878662109375e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.25371241569519043s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.0279159545898438e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 5.9604644775390625e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.6469383239746094s
Availability | SPARQL endpoint availability check for Demografie took 4.267692565917969e-05s
Availability | VoID file availability check for Demografie took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Demografie took 0.2433631420135498s
Reputation | Calculation of the PageRank for Demografie took 0.02158379554748535s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0008032321929931641s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.552436828613281e-05s
Believability | Calculation of trust value for Demografie took 6.4373016357421875e-06s
INFO | --- Analysis for demografie took 2.6443896293640137s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.410743713378906e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2409038543701172s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.647804260253906e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 6.198883056640625e-06s
INFO | --- Analysis for desaparecidos took 2.5331735610961914s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.9591064453125e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.24452972412109375s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020101547241210938s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.989738464355469e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 8.344650268554688e-06s
INFO | --- Analysis for deustoentrepreneurship took 3.806617021560669s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.2438507080078125e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0005886554718017578s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.24268603324890137s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.0001087188720703125s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.62939453125e-06s
INFO | --- Analysis for deustotech took 3.7441554069519043s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 0.7963156700134277s
Availability | VoID file availability check for Deutsche Biographie took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.23557519912719727s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.933906555175781e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.152557373046875e-06s
INFO | --- Analysis for deutsche-biographie took 3.050601005554199s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 5.793571472167969e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2419147491455078s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.698204040527344e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 5.9604644775390625e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.586644887924194s
Availability | SPARQL endpoint availability check for dev8d took 4.2438507080078125e-05s
Availability | VoID file availability check for dev8d took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for dev8d took 0.24090266227722168s
Reputation | Calculation of the PageRank for dev8d took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for dev8d took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for dev8d took 7.152557373046875e-05s
Believability | Calculation of trust value for dev8d took 6.9141387939453125e-06s
INFO | --- Analysis for dev8d took 2.5045723915100098s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.20548129081726s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0006363391876220703s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.2505028247833252s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.435943603515625e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 6.9141387939453125e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.7890899181366s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.4345855712890625e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.26679086685180664s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.0994415283203125e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 8.106231689453125e-06s
INFO | --- Analysis for DHSVM took 17.607677221298218s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.410743713378906e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.23771023750305176s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007283687591552734s
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 1.1682510375976562e-05s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.6742568016052246s
Availability | SPARQL endpoint availability check for Diavgeia took 4.76837158203125e-05s
Availability | VoID file availability check for Diavgeia took 0.0008256435394287109s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.24421119689941406s
Reputation | Calculation of the PageRank for Diavgeia took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.96453857421875e-05s
Believability | Calculation of trust value for Diavgeia took 4.5299530029296875e-06s
INFO | --- Analysis for diavgeia took 6.0865349769592285s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.363059997558594e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.24353909492492676s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011801719665527344s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0251998901367188e-05s
INFO | --- Analysis for didactalia took 15.060961484909058s
Availability | SPARQL endpoint availability check for diigo.feed took 4.1484832763671875e-05s
Availability | VoID file availability check for diigo.feed took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.23759174346923828s
Reputation | Calculation of the PageRank for diigo.feed took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.170967102050781e-05s
Believability | Calculation of trust value for diigo.feed took 6.67572021484375e-06s
INFO | --- Analysis for diigo-feed took 2.610330104827881s
Availability | SPARQL endpoint availability check for DisGeNET took 0.7715377807617188s
Availability | VoID file availability check for DisGeNET took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.24461078643798828s
Reputation | Calculation of the PageRank for DisGeNET took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00015044212341308594s
Believability | Calculation of trust value for DisGeNET took 1.0728836059570312e-05s
INFO | --- Analysis for disgenet took 7.6980671882629395s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.076957702636719e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.2395186424255371s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 8.106231689453125e-06s
INFO | --- Analysis for disk took 2.6320266723632812s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.935264587402344e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.23857474327087402s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.24249267578125e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 6.4373016357421875e-06s
INFO | --- Analysis for distritos-zaragoza took 2.604033946990967s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.482269287109375e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.000751495361328125s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.24350976943969727s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.0279159545898438e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 6.198883056640625e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 7.987149238586426s
Availability | SPARQL endpoint availability check for DM2E took 4.291534423828125e-05s
Availability | VoID file availability check for DM2E took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for DM2E took 0.23932456970214844s
Reputation | Calculation of the PageRank for DM2E took 0.020671367645263672s
Interlinking | Calculation of Degree of Connection for DM2E took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011563301086425781s
Believability | Calculation of trust value for DM2E took 5.9604644775390625e-06s
INFO | --- Analysis for dm2e took 2.922241449356079s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.124641418457031e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.2348473072052002s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.170967102050781e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 1.0728836059570312e-05s
INFO | --- Analysis for dmoz_rdf_dump took 2.621577262878418s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.562953233718872s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006113052368164062s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.27999448776245117s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001571178436279297s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 6.198883056640625e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 10.437642335891724s
Availability | SPARQL endpoint availability check for DOAP Store took 4.1484832763671875e-05s
Availability | VoID file availability check for DOAP Store took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.23976635932922363s
Reputation | Calculation of the PageRank for DOAP Store took 0.020815134048461914s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.4332275390625e-05s
Believability | Calculation of trust value for DOAP Store took 7.867813110351562e-06s
INFO | --- Analysis for doap_store took 2.6056694984436035s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 4.38690185546875e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.001567840576171875s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.24216938018798828s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.842613220214844e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 4.76837158203125e-06s
INFO | --- Analysis for doi took 6.9170982837677s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.363059997558594e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0006835460662841797s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2409956455230713s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.266334533691406e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.3589859008789062e-05s
INFO | --- Analysis for Driggu took 3.159261465072632s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.041116952896118s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0007798671722412109s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.34306836128234863s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.02075958251953125s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 4.744529724121094e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 6.198883056640625e-06s
INFO | --- Analysis for drug-data-hifm took 37.240169525146484s
Availability | SPARQL endpoint availability check for dspace took 7.319450378417969e-05s
Availability | VoID file availability check for dspace took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for dspace took 0.2385725975036621s
Reputation | Calculation of the PageRank for dspace took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for dspace took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for dspace took 3.361701965332031e-05s
Believability | Calculation of trust value for dspace took 6.67572021484375e-06s
INFO | --- Analysis for dspace took 2.62947940826416s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.220008850097656e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.2445988655090332s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.147125244140625e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 6.4373016357421875e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.633939743041992s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 271.99259305000305s
Availability | VoID file availability check for MetaLex Document Server took 0.0007128715515136719s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.24712204933166504s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 4.506111145019531e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.3909759521484375e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 557.293229341507s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.4590210914611816s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0003566741943359375s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.23868536949157715s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.172325134277344e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.152557373046875e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 14.93051815032959s
Availability | SPARQL endpoint availability check for DWS-Group took 4.1484832763671875e-05s
Availability | VoID file availability check for DWS-Group took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.24274897575378418s
Reputation | Calculation of the PageRank for DWS-Group took 0.020702123641967773s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010585784912109375s
Believability | Calculation of trust value for DWS-Group took 7.152557373046875e-06s
INFO | --- Analysis for dws-group took 2.3802037239074707s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.291534423828125e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0003726482391357422s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.23316597938537598s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.0202786922454834s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.528594970703125e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 6.67572021484375e-06s
INFO | --- Analysis for E1 took 4.144761085510254s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.08364701271057129s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.23977041244506836s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020032167434692383s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011134147644042969s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-alaska took 2.243626356124878s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.033005714416503906s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.24237942695617676s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.14984130859375e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-cau took 2.2291998863220215s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.034121036529541016s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00034880638122558594s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.6980149745941162s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.02097773551940918s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.961822509765625e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.6862893104553223s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.03878378868103027s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2406294345855713s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.021346330642700195s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.989738464355469e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 5.7220458984375e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.247650384902954s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.03295302391052246s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.2385110855102539s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013136863708496094s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 5.4836273193359375e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.2489371299743652s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.03412961959838867s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.24033522605895996s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.320808410644531e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 9.298324584960938e-06s
INFO | --- Analysis for eagle-i-famu took 2.2248520851135254s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04790329933166504s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.2384653091430664s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.021157503128051758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013065338134765625s
Believability | Calculation of trust value for eagle-i @ Harvard University took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-harvard took 2.250166654586792s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0635981559753418s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0003407001495361328s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.24162673950195312s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.02079010009765625s
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.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012874603271484375s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.241142749786377s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.039467811584472656s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0008788108825683594s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.23803496360778809s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.508827209472656e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-howard took 2.231217622756958s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.044415950775146484s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.23974204063415527s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.413459777832031e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.245968818664551s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.04209780693054199s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00037169456481933594s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.23623394966125488s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011420249938964844s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-jsu took 2.2495157718658447s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.031388044357299805s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.24104547500610352s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.02082347869873047s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 5.936622619628906e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-meharry took 2.2450387477874756s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.0400087833404541s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0003437995910644531s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.23682022094726562s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.799003601074219e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-montana took 2.229135513305664s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.0356745719909668s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.24229025840759277s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 0.00010061264038085938s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-msm took 2.24519681930542s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.044730186462402344s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.24381518363952637s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02031540870666504s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001239776611328125s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.2567780017852783s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.031920433044433594s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2471921443939209s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020331621170043945s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.175041198730469e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-psm took 2.2346761226654053s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.03987002372741699s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.23976945877075195s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.198883056640625e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-tsu took 2.257094383239746s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.0396728515625s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2360389232635498s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.365776062011719e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 6.67572021484375e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.235100746154785s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.038945674896240234s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.24071431159973145s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010013580322265625s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.214775323867798s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.04237771034240723s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.24110174179077148s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00013208389282226562s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-upr took 2.25846791267395s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.0532069206237793s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.23801875114440918s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 5.9604644775390625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-utep took 2.243522882461548s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.03129267692565918s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.23674964904785156s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 8.058547973632812e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-utsa took 2.220148801803589s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.14290356636047363s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.24115443229675293s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.298324584960938e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.4066696166992188e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 2.3659157752990723s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.042273521423339844s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.24000167846679688s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020246505737304688s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.128715515136719e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-xula took 2.264317512512207s
Availability | SPARQL endpoint availability check for Emergency situation took 0.7635695934295654s
Availability | VoID file availability check for Emergency situation took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.245574951171875s
Reputation | Calculation of the PageRank for Emergency situation took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for Emergency situation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.601478576660156e-05s
Believability | Calculation of trust value for Emergency situation took 1.0013580322265625e-05s
INFO | --- Analysis for Earthquake took 3.458679676055908s
Availability | SPARQL endpoint availability check for ESO took 0.6066160202026367s
Availability | VoID file availability check for ESO took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for ESO took 0.239790678024292s
Reputation | Calculation of the PageRank for ESO took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for ESO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ESO took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for ESO took 8.225440979003906e-05s
Believability | Calculation of trust value for ESO took 6.67572021484375e-06s
INFO | --- Analysis for Earthquake_case took 3.7219626903533936s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.3698420524597168s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.23901963233947754s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010848045349121094s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.245208740234375e-06s
INFO | --- Analysis for ecb-linked-data took 2.5527849197387695s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.177978277206421s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.24579787254333496s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.886222839355469e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 6.4373016357421875e-06s
INFO | --- Analysis for ecb-statistics-linked-data took 9.628983974456787s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.6294779777526855s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.23853778839111328s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02040696144104004s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.628036499023438e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 8.344650268554688e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.433010578155518s
Availability | SPARQL endpoint availability check for ECLAP took 20.652398824691772s
Availability | VoID file availability check for ECLAP took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for ECLAP took 0.23792314529418945s
Reputation | Calculation of the PageRank for ECLAP took 0.020171165466308594s
Interlinking | Calculation of Degree of Connection for ECLAP took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ECLAP took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.647804260253906e-05s
Believability | Calculation of trust value for ECLAP took 5.7220458984375e-06s
INFO | --- Analysis for eclap took 53.26477813720703s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 5.7220458984375e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2409350872039795s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.0967254638671875e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 6.198883056640625e-06s
INFO | --- Analysis for ECNU-GISer took 3.70280385017395s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.76837158203125e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2396700382232666s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02083301544189453s
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.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 6.508827209472656e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 7.62939453125e-06s
INFO | --- Analysis for ecs took 2.436433792114258s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.291534423828125e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.23443341255187988s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 2.86102294921875e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 6.67572021484375e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.658170223236084s
Availability | SPARQL endpoint availability check for Edublogs took 4.220008850097656e-05s
Availability | VoID file availability check for Edublogs took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Edublogs took 0.24300479888916016s
Reputation | Calculation of the PageRank for Edublogs took 0.02017998695373535s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010061264038085938s
Believability | Calculation of trust value for Edublogs took 1.0967254638671875e-05s
INFO | --- Analysis for edublogs took 2.9969139099121094s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.5143828392028809s
Availability | VoID file availability check for education.data.gov.uk took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.24096250534057617s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.083747863769531e-05s
Believability | Calculation of trust value for education.data.gov.uk took 6.9141387939453125e-06s
INFO | --- Analysis for education-data-gov-uk took 4.10358452796936s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.839897155761719e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2440204620361328s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 2.9087066650390625e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.62939453125e-06s
INFO | --- Analysis for education-openuplabs took 2.6532483100891113s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 393.7652220726013s
Availability | VoID file availability check for Educational programs - SISVU took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.8585295677185059s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.269050598144531e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 6.4373016357421875e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1321.9870946407318s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.7777178287506104s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.6723117828369141s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.695487976074219e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 4.76837158203125e-06s
INFO | --- Analysis for eea took 8.997172832489014s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.511873722076416s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.24206018447875977s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.245208740234375e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 4.5299530029296875e-06s
INFO | --- Analysis for eea-rod took 5.936761140823364s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.1479036808013916s
Availability | VoID file availability check for EEA Vocabularies took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.23592543601989746s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.320808410644531e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.152557373046875e-06s
INFO | --- Analysis for eea-vocabularies took 4.72688102722168s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.363059997558594e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.2407209873199463s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.314018249511719e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for ege-university-linked-open-data took 2.648707389831543s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.37741589546203613s
Availability | VoID file availability check for E-Government Ontology took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.24329304695129395s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for E-Government Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for EGovOntology took 3.119032859802246s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6337251663208008s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0005676746368408203s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.6269147396087646s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2926201820373535s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6506292819976807s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8695640563964844s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.334728956222534s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.638624429702759s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4411051273345947s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.8205316066741943s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24744081497192383s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.40016722679138184s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 6.336127758026123s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2387561798095703s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3455207347869873s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.574080228805542s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3122742176055908s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.28542304039001465s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29275012016296387s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 11.376795530319214s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 7.43865966796875e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2926974296569824s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2604517936706543s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.35635972023010254s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2341933250427246s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.99723219871521s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.8075487613677979s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5338616371154785s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.602299928665161s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23554778099060059s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.32604289054870605s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2854452133178711s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2209076881408691s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030029773712158203s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.028638124465942383s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2349700927734375s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.336874485015869s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.443497896194458s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.237330913543701s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1659045219421387s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.017626047134399s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.033374786376953125s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.42201852798461914s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4889805316925049s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3095.3749091625214s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.4851438999176025s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.435943603515625e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.430511474609375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 7.3909759521484375e-06s
INFO | --- Analysis for ei2a took 16402.16643333435s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.4345855712890625e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.24195194244384766s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010752677917480469s
Believability | Calculation of trust value for EIONET RDF Data took 5.0067901611328125e-06s
INFO | --- Analysis for eionet-rdf took 3.222395181655884s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.553794860839844e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.23793745040893555s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020345687866210938s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0040740966796875e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 8.821487426757812e-06s
INFO | --- Analysis for ElgooG_ took 2.6088523864746094s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.3392181396484375e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.24312257766723633s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.0208737850189209s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.4332275390625e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.3909759521484375e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.6404929161071777s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 9.22037410736084s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.24199652671813965s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 0.00010585784912109375s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.049041748046875e-05s
INFO | --- Analysis for elviajero took 24.792078018188477s
Availability | SPARQL endpoint availability check for EMN took 4.315376281738281e-05s
Availability | VoID file availability check for EMN took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for EMN took 0.24274325370788574s
Reputation | Calculation of the PageRank for EMN took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for EMN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EMN took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for EMN took 4.00543212890625e-05s
Believability | Calculation of trust value for EMN took 6.67572021484375e-06s
INFO | --- Analysis for emn took 2.5447652339935303s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.24265027046203613s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.125999450683594e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 4.5299530029296875e-06s
INFO | --- Analysis for enakting-co2emission took 2.202965259552002s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.23710966110229492s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 3.933906555175781e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-crime took 2.2495439052581787s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.24698734283447266s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.933906555175781e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 4.291534423828125e-06s
INFO | --- Analysis for enakting-energy took 2.179999589920044s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.24767351150512695s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 8.702278137207031e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 4.291534423828125e-06s
INFO | --- Analysis for enakting-mortality took 2.200147867202759s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.24059176445007324s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.695487976074219e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 3.814697265625e-06s
INFO | --- Analysis for enakting-nhs took 2.2028212547302246s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2396836280822754s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020921945571899414s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.698204040527344e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.7220458984375e-06s
INFO | --- Analysis for enakting-population took 2.165428400039673s
Availability | SPARQL endpoint availability check for Enel Shops took 4.410743713378906e-05s
Availability | VoID file availability check for Enel Shops took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.23540759086608887s
Reputation | Calculation of the PageRank for Enel Shops took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for Enel Shops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.0517578125e-05s
Believability | Calculation of trust value for Enel Shops took 6.198883056640625e-06s
INFO | --- Analysis for enel-shops took 2.5819201469421387s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.458427429199219e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.25898194313049316s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.4332275390625e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 8.58306884765625e-06s
INFO | --- Analysis for energy-efficiency took 2.657888650894165s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.23885512351989746s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.0040740966796875e-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.6236703395843506s
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.0002262592315673828s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2452526092529297s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 2.8371810913085938e-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.647547960281372s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.23382973670959473s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.8371810913085938e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 8.821487426757812e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.647432327270508s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.506111145019531e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.25408005714416504s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.0209503173828125s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.2901763916015625e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 8.344650268554688e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.66538405418396s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.23894095420837402s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.637730121612549s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00021600723266601562s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.23986554145812988s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02037835121154785s
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.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.685617685317993s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.458427429199219e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.24170398712158203s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020964860916137695s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.528594970703125e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 8.821487426757812e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.658302068710327s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.6624178886413574s
Availability | VoID file availability check for English Heritage Periods List took 0.0006263256072998047s
Extra | Recovery of all triples for English Heritage Periods List took 0.4066305160522461s
Performance | Total latancy measurement for English Heritage Periods List took 1.933429479598999s
Amount of data | Number of triples check for English Heritage Periods List took 0.5957732200622559s
Versatility | Languages check for English Heritage Periods List took 0.33109593391418457s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.6633098125457764s
Security | Check HTTPS for English Heritage Periods List took 0.24498319625854492s
Interpretability | RDF structures check for English Heritage Periods List took 0.33452272415161133s
Versatility | Serialization formats check for English Heritage Periods List took 0.517289400100708s
Availability | RDF dump link check for English Heritage Periods List took 0.37680745124816895s
License | MR license check for English Heritage Periods List took 0.48455357551574707s
License | HR license check for English Heritage Periods List took 0.41884660720825195s
Amount of data | Number of property check for English Heritage Periods List took 0.4120817184448242s
Understandability | Number of label check for English Heritage Periods List took 0.46122241020202637s
Understandability | URI regex check for English Heritage Periods List took 0.7332940101623535s
Understandability | Vocabs check for English Heritage Periods List took 0.4157884120941162s
Verifiability | Authors check for English Heritage Periods List took 0.4147486686706543s
Verifiability | Publishers check for English Heritage Periods List took 0.43184328079223633s
Performance | Throughput check for English Heritage Periods List took 11.339637756347656s
Amount of data | Check the number of entities for English Heritage Periods List took 7.486343383789062e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.4571554660797119s
Interlinking | sameAs chians check for English Heritage Periods List took 0.41487598419189453s
Interlinking | skos check for English Heritage Periods List took 0.37844014167785645s
Interlinking | skos check for English Heritage Periods List took 0.4055042266845703s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.5672383308410645s
Currency | Creation date check for English Heritage Periods List took 0.7548251152038574s
Currency | Modification date check for English Heritage Periods List took 0.9543724060058594s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8791143894195557s
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.42796874046325684s
Accuracy | Check Functional Property for English Heritage Periods List took 0.3844873905181885s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3755061626434326s
Consistency | Disjoint class check for English Heritage Periods List took 0.36673617362976074s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.38054633140563965s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.5738179683685303s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00016999244689941406s
Security | Sign check for English Heritage Periods List took 0.4400019645690918s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.24839472770690918s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.02076101303100586s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.430511474609375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-periods-list took 57.81487798690796s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 0.7788281440734863s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.23877787590026855s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.528594970703125e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 5.4836273193359375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 3.474959373474121s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.15265440940856934s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.23827171325683594s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.5762786865234375e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.4836273193359375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 3.230391263961792s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.172325134277344e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.24103403091430664s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 6.4373016357421875e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.655418634414673s
Availability | SPARQL endpoint availability check for English WordNet took 4.363059997558594e-05s
Availability | VoID file availability check for English WordNet took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for English WordNet took 0.2447676658630371s
Reputation | Calculation of the PageRank for English WordNet took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0007643699645996094s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.4809112548828125e-05s
Believability | Calculation of trust value for English WordNet took 7.62939453125e-06s
INFO | --- Analysis for english-wordnet took 2.7117767333984375s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.23929333686828613s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Places took 7.62939453125e-06s
INFO | --- Analysis for englishheritage_places took 2.6451351642608643s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.16623759269714355s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.244279146194458s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 9.775161743164062e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 8.58306884765625e-06s
INFO | --- Analysis for enipedia took 2.37371563911438s
Availability | SPARQL endpoint availability check for Enslaved.org took 7.271766662597656e-05s
Availability | VoID file availability check for Enslaved.org took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2410130500793457s
Reputation | Calculation of the PageRank for Enslaved.org took 0.021013259887695312s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.314018249511719e-05s
Believability | Calculation of trust value for Enslaved.org took 6.198883056640625e-06s
INFO | --- Analysis for enslaved.org took 5.092283725738525s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.059389352798461914s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00036978721618652344s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.23852157592773438s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.02087855339050293s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 6.0558319091796875e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 5.4836273193359375e-06s
INFO | --- Analysis for entice-graph took 2.238035202026367s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.458427429199219e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007700920104980469s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.23998761177062988s
Reputation | Calculation of the PageRank for Entrez Gene took 0.021549463272094727s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.001085519790649414s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 4.696846008300781e-05s
Believability | Calculation of trust value for Entrez Gene took 1.2159347534179688e-05s
INFO | --- Analysis for entrez_gene took 28.323625802993774s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.1484832763671875e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.23949098587036133s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.24249267578125e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene_extract took 2.621936082839966s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 0.9944348335266113s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.24541759490966797s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.054473876953125e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 8.58306884765625e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 10.823041915893555s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.27825427055358887s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.24042320251464844s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020546674728393555s
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.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.744529724121094e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 9.298324584960938e-06s
INFO | --- Analysis for environment-data-gov-uk took 8.915470361709595s
Availability | SPARQL endpoint availability check for EARTh took 272.2670831680298s
Availability | VoID file availability check for EARTh took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for EARTh took 0.2391209602355957s
Reputation | Calculation of the PageRank for EARTh took 0.020771265029907227s
Interlinking | Calculation of Degree of Connection for EARTh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EARTh took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00011348724365234375s
Believability | Calculation of trust value for EARTh took 8.344650268554688e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 563.745364189148s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.5852844715118408s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00023984909057617188s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 115.3084146976471s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.9947187900543213s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 8.46327018737793s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 14.603356838226318s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.20478415489197s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 2.4425454139709473s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.2763326168060303s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 12.467646598815918s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.28543663024902344s
License | MR license check for Micka (EO metadata) @PSNC took 0.6060154438018799s
License | HR license check for Micka (EO metadata) @PSNC took 300.2274503707886s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.2934744358062744s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 3.263603925704956s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.7791087627410889s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.4114723205566406s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.19214630126953125s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.24380183219909668s
Performance | Throughput check for Micka (EO metadata) @PSNC took 10.751892805099487s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 0.0001266002655029297s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.1860041618347168s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.1875767707824707s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.5393335819244385s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.4970989227294922s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 5.4244914054870605s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.484999418258667s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2137312889099121s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 155.32690596580505s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.18369746208190918s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.3633849620819092s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.36037182807922363s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 40.0871467590332s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.7097346782684326s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.668494939804077s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.17999267578125s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 81.08452582359314s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.396957874298096s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 33.136438608169556s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.2737631797790527s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 82.07207465171814s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.7294504642486572s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.6019036769866943s
Security | Sign check for Micka (EO metadata) @PSNC took 0.4575181007385254s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 9.80153751373291s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.864534854888916s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021038532257080078s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.933906555175781e-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.867813110351562e-06s
INFO | --- Analysis for EO_metadata took 2230.1832976341248s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.506111145019531e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.6787536144256592s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020733356475830078s
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.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.337860107421875e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.3909759521484375e-06s
INFO | --- Analysis for EOKP-Datasets took 5.304248332977295s
Availability | SPARQL endpoint availability check for EPA-CDR took 0.00017333030700683594s
Availability | VoID file availability check for EPA-CDR took 0.0007088184356689453s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.24522662162780762s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0009539127349853516s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 4.0531158447265625e-05s
Believability | Calculation of trust value for EPA-CDR took 4.76837158203125e-06s
INFO | --- Analysis for epa-cdr took 7.991028785705566s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.363059997558594e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.24170422554016113s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.009506225585938e-05s
Believability | Calculation of trust value for EPA-FRS took 5.4836273193359375e-06s
INFO | --- Analysis for epa-frs took 6.7031872272491455s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.38690185546875e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.6765246391296387s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.3855438232421875e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.245208740234375e-06s
INFO | --- Analysis for epa-rcra took 6.0548646450042725s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.220008850097656e-05s
Availability | VoID file availability check for EPA-SRS took 0.0003647804260253906s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.24597930908203125s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.43865966796875e-05s
Believability | Calculation of trust value for EPA-SRS took 4.76837158203125e-06s
INFO | --- Analysis for epa-srs took 5.701035499572754s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.458427429199219e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.24082589149475098s
Reputation | Calculation of the PageRank for EPA-TRI took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.910064697265625e-05s
Believability | Calculation of trust value for EPA-TRI took 5.0067901611328125e-06s
INFO | --- Analysis for epa-tri took 5.649911642074585s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.172325134277344e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.2401139736175537s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020372390747070312s
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.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.176399230957031e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 7.152557373046875e-06s
INFO | --- Analysis for epo took 2.656402826309204s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.06119704246520996s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2561476230621338s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00012493133544921875s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.738574743270874s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.43236207962036133s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.2332627773284912s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02104973793029785s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.320808410644531e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 5.9604644775390625e-06s
INFO | --- Analysis for eprtr took 3.291407585144043s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.859384298324585s
Availability | VoID file availability check for Railway Infrastructure KG took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.23812508583068848s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.170967102050781e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 6.9141387939453125e-06s
INFO | --- Analysis for ERAKG took 3.0466790199279785s
Availability | SPARQL endpoint availability check for reg took 4.363059997558594e-05s
Availability | VoID file availability check for reg took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for reg took 0.23603081703186035s
Reputation | Calculation of the PageRank for reg took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for reg took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for reg took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for reg took 1.049041748046875e-05s
Believability | Calculation of trust value for reg took 1.0728836059570312e-05s
INFO | --- Analysis for erg took 2.133585214614868s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.24120640754699707s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.24070048332214355s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02012467384338379s
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.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 2.8133392333984375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 4.76837158203125e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.6257596015930176s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 5.1975250244140625e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.24044227600097656s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020761728286743164s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.012222290039062e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 9.059906005859375e-06s
INFO | --- Analysis for esd-standards took 3.6619479656219482s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.458427429199219e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.24107885360717773s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.510185241699219e-05s
Believability | Calculation of trust value for ESD-Toolkit took 5.4836273193359375e-06s
INFO | --- Analysis for esd-toolkit took 2.986328125s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.291534423828125e-05s
Availability | VoID file availability check for Dataset Esis took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.2431201934814453s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020929574966430664s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.337860107421875e-05s
Believability | Calculation of trust value for Dataset Esis took 7.867813110351562e-06s
INFO | --- Analysis for esislearning took 2.5703537464141846s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.291534423828125e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.24615693092346191s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.24249267578125e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 6.9141387939453125e-06s
INFO | --- Analysis for ESV took 3.8766262531280518s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.4391443729400635s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.23791170120239258s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 3.6075868606567383s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.049114465713501s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.23961329460144043s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.987022399902344e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 6.4373016357421875e-06s
INFO | --- Analysis for eu-agencies-bodies took 11.512432336807251s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.267692565917969e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.24123787879943848s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.1948089599609375e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 6.4373016357421875e-06s
INFO | --- Analysis for eu-dgt-tm took 2.6361420154571533s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.9114227294921875e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0007302761077880859s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.24389934539794922s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.772445678710938e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 4.5299530029296875e-06s
INFO | --- Analysis for eu-institutions took 5.254609107971191s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.7658469676971436s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.24585986137390137s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.552436828613281e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.9604644775390625e-06s
INFO | --- Analysis for eu-parliament-media took 5.804539203643799s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.7998824119567871s
Availability | VoID file availability check for EU Who Is Who took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.24247121810913086s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 8.535385131835938e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.7220458984375e-06s
INFO | --- Analysis for eu-who-is-who took 7.9841086864471436s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 1.024876356124878s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0007140636444091797s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.23956608772277832s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.02011847496032715s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.0531158447265625e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for eumida-linked-data took 7.7218217849731445s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.29114818572998047s
Availability | VoID file availability check for European Nature Information System took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.23902273178100586s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020432472229003906s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007388591766357422s
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.62939453125e-06s
INFO | --- Analysis for eunis took 3.9418106079101562s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 3.739321708679199s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006418228149414062s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.23893523216247559s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020991086959838867s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.581710815429688e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for eur-lex-rdf took 10.805795192718506s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.6501033306121826s
Availability | VoID file availability check for Standard Eurobarometer took 0.0014431476593017578s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.24298429489135742s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.0205078125s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.291534423828125e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 5.7220458984375e-06s
INFO | --- Analysis for eurobarometer-standard took 6.88561224937439s
Availability | SPARQL endpoint availability check for European Election Results took 0.7360231876373291s
Availability | VoID file availability check for European Election Results took 0.0007731914520263672s
Completeness | Calculation of interlinking completeness for European Election Results took 0.24540066719055176s
Reputation | Calculation of the PageRank for European Election Results took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for European Election Results took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Election Results took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.5762786865234375e-05s
Believability | Calculation of trust value for European Election Results took 4.291534423828125e-06s
INFO | --- Analysis for european-election-results took 6.950917720794678s
Availability | SPARQL endpoint availability check for EPO patents took 0.3553316593170166s
Availability | VoID file availability check for EPO patents took 0.0006153583526611328s
Extra | Recovery of all triples for EPO patents took 37.33914804458618s
Performance | Total latancy measurement for EPO patents took 0.8966357707977295s
Amount of data | Number of triples check for EPO patents took 90.19216561317444s
Versatility | Languages check for EPO patents took 120.12659406661987s
Interpretability | Number of blank nodes check for EPO patents took 90.31213903427124s
Interpretability | RDF structures check for EPO patents took 0.17114710807800293s
Versatility | Serialization formats check for EPO patents took 0.25290417671203613s
Availability | RDF dump link check for EPO patents took 0.173872709274292s
License | MR license check for EPO patents took 0.1648409366607666s
License | HR license check for EPO patents took 90.16393613815308s
Amount of data | Number of property check for EPO patents took 0.2225801944732666s
Understandability | Number of label check for EPO patents took 90.19393301010132s
Understandability | URI regex check for EPO patents took 0.5609524250030518s
Understandability | Vocabs check for EPO patents took 0.22705793380737305s
Verifiability | Authors check for EPO patents took 0.2569465637207031s
Verifiability | Publishers check for EPO patents took 0.20153427124023438s
Performance | Throughput check for EPO patents took 10.997394323348999s
Amount of data | Check the number of entities for EPO patents took 3.170967102050781e-05s
Verifiability | Contribs. check for EPO patents took 0.14635157585144043s
Interlinking | sameAs chians check for EPO patents took 0.15292763710021973s
Interlinking | skos check for EPO patents took 0.17800092697143555s
Interlinking | skos check for EPO patents took 0.16727662086486816s
Timeliness | dataset update frequency check for EPO patents took 0.14385151863098145s
Currency | Creation date check for EPO patents took 0.44042325019836426s
Currency | Modification date check for EPO patents took 0.31768250465393066s
Rep.Conc. | URIs length for EPO patents took 159.2275195121765s
Interoperability | New vocabularies check for EPO patents took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.2659010887145996s
Accuracy | Check Empty annotation labels for EPO patents took 18.789092540740967s
Accuracy | Check White space in annotation for EPO patents took 3.000791072845459s
Accuracy | Check Datatype consistency for EPO patents took 4.908867359161377s
Consistency | Disjoint class check for EPO patents took 0.21183252334594727s
Consistency | Check Misplaced properties for EPO patents took 120.39968466758728s
Consistency | Check Ontology hijacking for EPO patents took 20.7661874294281s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.48148512840271s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.42022919654846s
Conciseness | Check Extensional conciseness for EPO patents took 2.8188278675079346s
Conciseness | Check Intensional conciseness for EPO patents took 0.39426493644714355s
Security | Sign check for EPO patents took 0.2573120594024658s
Availability | Check URIs Dereferenciability for EPO patents took 1.7514936923980713s
Completeness | Calculation of interlinking completeness for EPO patents took 1.1421561241149902s
Reputation | Calculation of the PageRank for EPO patents took 0.020902395248413086s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for EPO patents took 4.4345855712890625e-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 7.3909759521484375e-06s
INFO | --- Analysis for European_Patent_Information took 1308.830750465393s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 6.866455078125e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.6710624694824219s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for europeana-lod took 3.928537368774414s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.315376281738281e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.2825491428375244s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0009639263153076172s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 0.00010633468627929688s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 9.298324584960938e-06s
INFO | --- Analysis for europeana-lod-v1 took 9.140502452850342s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.02544403076171875s
Availability | VoID file availability check for Europeana SPARQL took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.6771986484527588s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.6253204345703125e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.152557373046875e-06s
INFO | --- Analysis for europeana-sparql took 4.0465734004974365s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.07890915870666504s
Availability | VoID file availability check for EuroSentiment took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.29036951065063477s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020467281341552734s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 4.172325134277344e-05s
Believability | Calculation of trust value for EuroSentiment took 7.152557373046875e-06s
INFO | --- Analysis for eurosentiment took 2.974013090133667s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 5.054473876953125e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.24075651168823242s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020175695419311523s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.843971252441406e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 4.76837158203125e-06s
INFO | --- Analysis for eurostat-rdf took 16.14700675010681s
Availability | SPARQL endpoint availability check for EuroVoc took 0.2779245376586914s
Availability | VoID file availability check for EuroVoc took 0.0006196498870849609s
Extra | Recovery of all triples for EuroVoc took 96.97519016265869s
Performance | Total latancy measurement for EuroVoc took 0.5611724853515625s
Amount of data | Number of triples check for EuroVoc took 100.83113050460815s
Interoperability | New terms check for EuroVoc took 91.0072832107544s
Versatility | Languages check for EuroVoc took 300.1379942893982s
Interpretability | Number of blank nodes check for EuroVoc took 1.3342761993408203s
Security | Check HTTPS for EuroVoc took 0.28781628608703613s
Interpretability | RDF structures check for EuroVoc took 0.36838746070861816s
Versatility | Serialization formats check for EuroVoc took 3.6416609287261963s
Availability | RDF dump link check for EuroVoc took 0.2110462188720703s
License | MR license check for EuroVoc took 0.2519230842590332s
License | HR license check for EuroVoc took 300.0346574783325s
Amount of data | Number of property check for EuroVoc took 0.1543576717376709s
Understandability | Number of label check for EuroVoc took 6.691113471984863s
Understandability | URI regex check for EuroVoc took 0.23914551734924316s
Understandability | Vocabs check for EuroVoc took 0.10712766647338867s
Verifiability | Authors check for EuroVoc took 0.17929291725158691s
Verifiability | Publishers check for EuroVoc took 0.21245813369750977s
Performance | Throughput check for EuroVoc took 10.409117460250854s
Amount of data | Check the number of entities for EuroVoc took 6.914138793945312e-05s
Verifiability | Contribs. check for EuroVoc took 0.2225341796875s
Interlinking | sameAs chians check for EuroVoc took 10.552413940429688s
Interlinking | skos check for EuroVoc took 0.45773816108703613s
Interlinking | skos check for EuroVoc took 0.4211239814758301s
Timeliness | dataset update frequency check for EuroVoc took 0.2638208866119385s
Currency | Creation date check for EuroVoc took 0.4970841407775879s
Currency | Modification date check for EuroVoc took 0.21511054039001465s
Rep.Conc. | URIs length for EuroVoc took 569.4941008090973s
Interoperability | New vocabularies check for EuroVoc took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.14255213737487793s
Accuracy | Check Functional Property for EuroVoc took 0.1898353099822998s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.1692357063293457s
Accuracy | Check Empty annotation labels for EuroVoc took 21.94374990463257s
Accuracy | Check White space in annotation for EuroVoc took 3.094114065170288s
Accuracy | Check Datatype consistency for EuroVoc took 2.7055938243865967s
Consistency | Disjoint class check for EuroVoc took 0.18893742561340332s
Consistency | Check Misplaced properties for EuroVoc took 300.3567428588867s
Consistency | Misplaced classes for EuroVoc took 8.436738967895508s
Consistency | Check Ontology hijacking for EuroVoc took 30.923475980758667s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 11.315603494644165s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 301.29272866249084s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0318856239318848s
Conciseness | Check Intensional conciseness for EuroVoc took 0.4900946617126465s
Security | Sign check for EuroVoc took 0.15115666389465332s
Availability | Check URIs Dereferenciability for EuroVoc took 3.8472554683685303s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.0591118335723877s
Reputation | Calculation of the PageRank for EuroVoc took 0.0232236385345459s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.440017700195312e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.9073486328125e-06s
Believability | Calculation of trust value for EuroVoc took 8.106231689453125e-06s
INFO | --- Analysis for eurovoc took 14574.693859577179s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 6.794929504394531e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.6745216846466064s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.363059997558594e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.867813110351562e-06s
INFO | --- Analysis for eurovoc-in-skos took 4.4668145179748535s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.172325134277344e-05s
Availability | VoID file availability check for European Television Heritage took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.2426590919494629s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020291566848754883s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.9802322387695312e-05s
Believability | Calculation of trust value for European Television Heritage took 6.67572021484375e-06s
INFO | --- Analysis for euscreen took 3.640362024307251s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 6.341934204101562e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.24097466468811035s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020607948303222656s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.7206878662109375e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 1.8835067749023438e-05s
INFO | --- Analysis for euskadi-farmacias took 6.608823537826538s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7529957294464111s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.24672675132751465s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020649194717407227s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.218650817871094e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 7.152557373046875e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.677954435348511s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.2642993927001953s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0008399486541748047s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2435140609741211s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.581710815429688e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 6.9141387939453125e-06s
INFO | --- Analysis for eutc-productions took 6.533606767654419s
Availability | SPARQL endpoint availability check for EventMedia took 0.32939982414245605s
Availability | VoID file availability check for EventMedia took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2455005645751953s
Reputation | Calculation of the PageRank for EventMedia took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.0001068115234375s
Believability | Calculation of trust value for EventMedia took 7.3909759521484375e-06s
INFO | --- Analysis for event-media took 10.242070198059082s
Availability | SPARQL endpoint availability check for EventKG took 7.367134094238281e-05s
Availability | VoID file availability check for EventKG took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for EventKG took 0.24825692176818848s
Reputation | Calculation of the PageRank for EventKG took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for EventKG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.320808410644531e-05s
Believability | Calculation of trust value for EventKG took 5.245208740234375e-06s
INFO | --- Analysis for eventkg took 5.297276020050049s
Availability | SPARQL endpoint availability check for Eventseer took 0.7917499542236328s
Availability | VoID file availability check for Eventseer took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Eventseer took 0.24114608764648438s
Reputation | Calculation of the PageRank for Eventseer took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.935264587402344e-05s
Believability | Calculation of trust value for Eventseer took 6.67572021484375e-06s
INFO | --- Analysis for eventseer took 3.0177366733551025s
Availability | SPARQL endpoint availability check for Face Link took 4.458427429199219e-05s
Availability | VoID file availability check for Face Link took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for Face Link took 0.24080777168273926s
Reputation | Calculation of the PageRank for Face Link took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.600120544433594e-05s
Believability | Calculation of trust value for Face Link took 8.821487426757812e-06s
INFO | --- Analysis for Face_Link took 2.613285541534424s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.076957702636719e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2418525218963623s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.075599670410156e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 6.4373016357421875e-06s
INFO | --- Analysis for facebook-lids took 2.645172357559204s
Availability | SPARQL endpoint availability check for Fact Forge took 4.1484832763671875e-05s
Availability | VoID file availability check for Fact Forge took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.24041438102722168s
Reputation | Calculation of the PageRank for Fact Forge took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for Fact Forge took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.0517578125e-05s
Believability | Calculation of trust value for Fact Forge took 6.198883056640625e-06s
INFO | --- Analysis for fact-forge took 2.6301302909851074s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.46417999267578125s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00025844573974609375s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 119.55197811126709s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.8902652263641357s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.679271936416626s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 13.826228141784668s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.1711542606354s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.9168171882629395s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.27045416831970215s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.16762638092041s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21856188774108887s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.43362975120544434s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.1886763572693s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2978386878967285s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.2162766456604004s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9253463745117188s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4815406799316406s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2032933235168457s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.28565454483032227s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.453526735305786s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.009506225585938e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19789576530456543s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.20084452629089355s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4770011901855469s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.44698214530944824s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.688345909118652s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.45670056343078613s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2081139087677002s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 158.53793597221375s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.498512506484985s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.743655204772949s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.3399829864502s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.3473834991455s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 301.37523007392883s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.755091428756714s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.2185249328613s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.193437814712524s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.2625148296356201s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.6689300537109375e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 6.4373016357421875e-06s
INFO | --- Analysis for FADN_(2019) took 7674.212222337723s
Availability | SPARQL endpoint availability check for FAMEData took 4.863739013671875e-05s
Availability | VoID file availability check for FAMEData took 0.0006854534149169922s
Completeness | Calculation of interlinking completeness for FAMEData took 0.7955832481384277s
Reputation | Calculation of the PageRank for FAMEData took 0.020655393600463867s
Interlinking | Calculation of Degree of Connection for FAMEData took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FAMEData took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.552436828613281e-05s
Believability | Calculation of trust value for FAMEData took 7.3909759521484375e-06s
INFO | --- Analysis for famedata took 65.29521799087524s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 5.3882598876953125e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.6872515678405762s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 0.00010991096496582031s
Believability | Calculation of trust value for FAO geopolitical ontology took 5.4836273193359375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 14.426865816116333s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.5008208751678467s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.26378393173217773s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010132789611816406s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for fao-linked-data took 4.697636842727661s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.363059997558594e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.25562524795532227s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.02019786834716797s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 2.8371810913085938e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for FAO_species took 2.3763628005981445s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.507883548736572s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2742152214050293s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020226240158081055s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.5299530029296875e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.1682510375976562e-05s
INFO | --- Analysis for farmbio-chembl took 64.65332365036011s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.315376281738281e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.27007222175598145s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.266334533691406e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 1.1920928955078125e-05s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 3.749220132827759s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 7.414817810058594e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.26996850967407227s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.4809112548828125e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 7.152557373046875e-06s
INFO | --- Analysis for farolapp-dataset took 3.7489702701568604s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.124641418457031e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.26602625846862793s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020150423049926758s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.9802322387695312e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 8.106231689453125e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.9396214485168457s
Availability | SPARQL endpoint availability check for I4.0-Onto took 5.3882598876953125e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.26500511169433594s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.0279159545898438e-05s
Believability | Calculation of trust value for I4.0-Onto took 6.198883056640625e-06s
INFO | --- Analysis for fatimazahra took 2.4533801078796387s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.363059997558594e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.28738903999328613s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020209312438964844s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 6.67572021484375e-06s
INFO | --- Analysis for federal-economic-rdf took 2.9119880199432373s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.38690185546875e-05s
Availability | VoID file availability check for Feed Wrapper took 0.00032138824462890625s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.2578296661376953s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.02031707763671875s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.075599670410156e-05s
Believability | Calculation of trust value for Feed Wrapper took 7.152557373046875e-06s
INFO | --- Analysis for feedwrapper-lids took 2.885138988494873s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.220008850097656e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2677724361419678s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 2.9325485229492188e-05s
Believability | Calculation of trust value for FHIR STU3 took 7.152557373046875e-06s
INFO | --- Analysis for FHIR_STU3 took 3.0878078937530518s
Availability | SPARQL endpoint availability check for FiESTA took 4.363059997558594e-05s
Availability | VoID file availability check for FiESTA took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for FiESTA took 0.27782511711120605s
Reputation | Calculation of the PageRank for FiESTA took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.9577484130859375e-05s
Believability | Calculation of trust value for FiESTA took 7.867813110351562e-06s
INFO | --- Analysis for fiesta took 12.570643424987793s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.673004150390625e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.2495110034942627s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020632266998291016s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007805824279785156s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.24249267578125e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.4373016357421875e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.3862335681915283s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 6.818771362304688e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005869865417480469s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.281787633895874s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.0203244686126709s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.033348083496094e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 4.76837158203125e-06s
INFO | --- Analysis for finnish-municipalities took 6.1351540088653564s
Availability | SPARQL endpoint availability check for firmao took 4.1961669921875e-05s
Availability | VoID file availability check for firmao took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for firmao took 0.2642996311187744s
Reputation | Calculation of the PageRank for firmao took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for firmao took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for firmao took 3.0279159545898438e-05s
Believability | Calculation of trust value for firmao took 7.152557373046875e-06s
INFO | --- Analysis for firmao took 3.0642306804656982s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.3392181396484375e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.26731324195861816s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.021033287048339844s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.361701965332031e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 1.33514404296875e-05s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.8904755115509033s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.29094743728637695s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0002989768981933594s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 300.18599104881287s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 300.4719567298889s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.2851810455322s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 129.70592403411865s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 131.06280159950256s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 131.07525944709778s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 131.07424306869507s
License | MR license check for Norway fishery stocks dataset @PSNC took 131.0669882297516s
License | HR license check for Norway fishery stocks dataset @PSNC took 131.07163858413696s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 131.07165575027466s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 131.07239508628845s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 262.1475670337677s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 131.0715935230255s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 131.06909036636353s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 131.07624530792236s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 0.00014853477478027344s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 131.07232189178467s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 131.07420015335083s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 131.07178497314453s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 131.07261276245117s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 131.0697100162506s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 131.579350233078s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.23699212074279785s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 600.4975411891937s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 300.3708791732788s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 300.3090851306915s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 129.6294503211975s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 132.21923804283142s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 0.00016450881958007812s
Security | Sign check for Norway fishery stocks dataset @PSNC took 131.06733226776123s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 1.5799839496612549s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020868778228759766s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 7.152557373046875e-07s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 9461.665335893631s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.4345855712890625e-05s
Availability | VoID file availability check for Fishes of Texas took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.6708545684814453s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020811796188354492s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 0.00016379356384277344s
Believability | Calculation of trust value for Fishes of Texas took 8.106231689453125e-06s
INFO | --- Analysis for fishes-of-texas took 6.029069185256958s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.482269287109375e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0009832382202148438s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.7528784275054932s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.02079939842224121s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007946491241455078s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 0.00011491775512695312s
Believability | Calculation of trust value for flickr? wrappr took 8.106231689453125e-06s
INFO | --- Analysis for flickr-wrappr took 189.93961811065674s
Availability | SPARQL endpoint availability check for flickr.person took 5.0067901611328125e-05s
Availability | VoID file availability check for flickr.person took 0.00031685829162597656s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2670891284942627s
Reputation | Calculation of the PageRank for flickr.person took 0.020836591720581055s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.361701965332031e-05s
Believability | Calculation of trust value for flickr.person took 1.0013580322265625e-05s
INFO | --- Analysis for flickr_person took 4.2555084228515625s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.315376281738281e-05s
Availability | VoID file availability check for flickr.videoobject took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2669186592102051s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.021038055419921875s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.361701965332031e-05s
Believability | Calculation of trust value for flickr.videoobject took 8.58306884765625e-06s
INFO | --- Analysis for flickr_videoobject took 4.326135158538818s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.5299530029296875e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.28536272048950195s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.314018249511719e-05s
Believability | Calculation of trust value for Future land use simulation model took 8.106231689453125e-06s
INFO | --- Analysis for FLUS took 7.9283435344696045s
Availability | SPARQL endpoint availability check for Fly-TED took 4.8160552978515625e-05s
Availability | VoID file availability check for Fly-TED took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.26747965812683105s
Reputation | Calculation of the PageRank for Fly-TED took 0.020540475845336914s
Interlinking | Calculation of Degree of Connection for Fly-TED took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.743171691894531e-05s
Believability | Calculation of trust value for Fly-TED took 7.3909759521484375e-06s
INFO | --- Analysis for fly-ted took 3.364490032196045s
Availability | SPARQL endpoint availability check for FlyAtlas took 4.2438507080078125e-05s
Availability | VoID file availability check for FlyAtlas took 0.00042057037353515625s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.23557376861572266s
Reputation | Calculation of the PageRank for FlyAtlas took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.266334533691406e-05s
Believability | Calculation of trust value for FlyAtlas took 6.9141387939453125e-06s
INFO | --- Analysis for flyatlas took 4.141018867492676s
Availability | SPARQL endpoint availability check for Flybase took 5.779444456100464s
Availability | VoID file availability check for Flybase took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Flybase took 0.2629048824310303s
Reputation | Calculation of the PageRank for Flybase took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for Flybase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Flybase took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.457069396972656e-05s
Believability | Calculation of trust value for Flybase took 7.3909759521484375e-06s
INFO | --- Analysis for flybase took 14.509921550750732s
Availability | SPARQL endpoint availability check for Flyted took 1.5335354804992676s
Availability | VoID file availability check for Flyted took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for Flyted took 0.2629239559173584s
Reputation | Calculation of the PageRank for Flyted took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for Flyted took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.2901763916015625e-05s
Believability | Calculation of trust value for Flyted took 5.9604644775390625e-06s
INFO | --- Analysis for flyted took 11.61588191986084s
Availability | SPARQL endpoint availability check for Foodista took 0.949350118637085s
Availability | VoID file availability check for Foodista took 0.0007560253143310547s
Completeness | Calculation of interlinking completeness for Foodista took 0.2675027847290039s
Reputation | Calculation of the PageRank for Foodista took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Foodista took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Foodista took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9325485229492188e-05s
Believability | Calculation of trust value for Foodista took 7.867813110351562e-06s
INFO | --- Analysis for foodista took 9.349981307983398s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2922070026397705s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.26128339767456055s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.152557373046875e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 6.9141387939453125e-06s
INFO | --- Analysis for foodpedia took 2.7254486083984375s
Availability | SPARQL endpoint availability check for FORGE Course information took 4.2438507080078125e-05s
Availability | VoID file availability check for FORGE Course information took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.26700687408447266s
Reputation | Calculation of the PageRank for FORGE Course information took 0.021584272384643555s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0026700496673583984s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.695487976074219e-05s
Believability | Calculation of trust value for FORGE Course information took 7.152557373046875e-06s
INFO | --- Analysis for forge-course-information took 3.8305554389953613s
Availability | SPARQL endpoint availability check for FrameBase schema took 5.626678466796875e-05s
Availability | VoID file availability check for FrameBase schema took 0.0007135868072509766s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.28081345558166504s
Reputation | Calculation of the PageRank for FrameBase schema took 0.020323514938354492s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.3392181396484375e-05s
Believability | Calculation of trust value for FrameBase schema took 6.67572021484375e-06s
INFO | --- Analysis for framebase-schema took 2.9928464889526367s
Availability | SPARQL endpoint availability check for FrameNet took 4.9591064453125e-05s
Availability | VoID file availability check for FrameNet took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for FrameNet took 0.24776029586791992s
Reputation | Calculation of the PageRank for FrameNet took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for FrameNet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FrameNet took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.0517578125e-05s
Believability | Calculation of trust value for FrameNet took 7.152557373046875e-06s
INFO | --- Analysis for framenet took 2.887212038040161s
Availability | SPARQL endpoint availability check for Framester took 4.291534423828125e-05s
Availability | VoID file availability check for Framester took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for Framester took 0.26297950744628906s
Reputation | Calculation of the PageRank for Framester took 0.020636796951293945s
Interlinking | Calculation of Degree of Connection for Framester took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Framester took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Framester took 7.2479248046875e-05s
Believability | Calculation of trust value for Framester took 6.198883056640625e-06s
INFO | --- Analysis for framester took 3.5152428150177s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.5372347831726074s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.001194000244140625s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.24906039237976074s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.021398305892944336s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0011463165283203125s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 0.00012731552124023438s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for frb-linked-data took 2.9718589782714844s
Availability | SPARQL endpoint availability check for Freebase took 4.601478576660156e-05s
Availability | VoID file availability check for Freebase took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Freebase took 0.25795888900756836s
Reputation | Calculation of the PageRank for Freebase took 0.020226001739501953s
Interlinking | Calculation of Degree of Connection for Freebase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Freebase took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.0002684593200683594s
Believability | Calculation of trust value for Freebase took 1.239776611328125e-05s
INFO | --- Analysis for freebase took 4.82450532913208s
Availability | SPARQL endpoint availability check for Freeyork took 4.5299530029296875e-05s
Availability | VoID file availability check for Freeyork took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Freeyork took 0.2507026195526123s
Reputation | Calculation of the PageRank for Freeyork took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Freeyork took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Freeyork took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.000125885009765625s
Believability | Calculation of trust value for Freeyork took 7.62939453125e-06s
INFO | --- Analysis for freeyork-org took 2.9418530464172363s
Availability | SPARQL endpoint availability check for French School Program took 4.3392181396484375e-05s
Availability | VoID file availability check for French School Program took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for French School Program took 0.2555088996887207s
Reputation | Calculation of the PageRank for French School Program took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for French School Program took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.0279159545898438e-05s
Believability | Calculation of trust value for French School Program took 6.4373016357421875e-06s
INFO | --- Analysis for french-school-program took 2.884916067123413s
Availability | SPARQL endpoint availability check for French School System took 4.649162292480469e-05s
Availability | VoID file availability check for French School System took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for French School System took 0.2596874237060547s
Reputation | Calculation of the PageRank for French School System took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for French School System took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for French School System took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for French School System took 2.86102294921875e-05s
Believability | Calculation of trust value for French School System took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-system took 2.906186819076538s
Availability | SPARQL endpoint availability check for French TimeBank took 7.128715515136719e-05s
Availability | VoID file availability check for French TimeBank took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.2595252990722656s
Reputation | Calculation of the PageRank for French TimeBank took 0.02102971076965332s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.528594970703125e-05s
Believability | Calculation of trust value for French TimeBank took 8.58306884765625e-06s
INFO | --- Analysis for french-timebank took 2.954503059387207s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 307.51845383644104s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0006799697875976562s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.27040815353393555s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.021153688430786133s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 8.726119995117188e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.9604644775390625e-06s
INFO | --- Analysis for fu-berlin-cordis took 343.3875198364258s
Availability | SPARQL endpoint availability check for DailyMed took 15.422641038894653s
Availability | VoID file availability check for DailyMed took 0.0010118484497070312s
Completeness | Calculation of interlinking completeness for DailyMed took 0.31685805320739746s
Reputation | Calculation of the PageRank for DailyMed took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for DailyMed took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DailyMed took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for DailyMed took 0.00011849403381347656s
Believability | Calculation of trust value for DailyMed took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-dailymed took 886.5642602443695s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 910.6317875385284s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.25690126419067383s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.021039724349975586s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 2.5272369384765625e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.893013000488281e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 8.58306884765625e-06s
INFO | --- Analysis for fu-berlin-dblp took 940.4957122802734s
Availability | SPARQL endpoint availability check for Diseasome took 2.7017524242401123s
Availability | VoID file availability check for Diseasome took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Diseasome took 0.24586987495422363s
Reputation | Calculation of the PageRank for Diseasome took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00011897087097167969s
Believability | Calculation of trust value for Diseasome took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-diseasome took 16.573625087738037s
Availability | SPARQL endpoint availability check for DrugBank took 2.664850950241089s
Availability | VoID file availability check for DrugBank took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for DrugBank took 0.27454090118408203s
Reputation | Calculation of the PageRank for DrugBank took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011372566223144531s
Believability | Calculation of trust value for DrugBank took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-drugbank took 16.224547386169434s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 2.303813934326172s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2596268653869629s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020442724227905273s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.86102294921875e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 6.4373016357421875e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 9.234387397766113s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 6.591754913330078s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.25368189811706543s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.021118879318237305s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0009276866912841797s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 8.344650268554688e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-euraxess took 24.003610372543335s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 3.9269325733184814s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0006492137908935547s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2828245162963867s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.939338684082031e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 8.821487426757812e-06s
INFO | --- Analysis for fu-berlin-eures took 16.92869520187378s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 3.637453556060791s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.7398931980133057s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.703636169433594e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 23.017263412475586s
Availability | SPARQL endpoint availability check for MediCare took 2.4314146041870117s
Availability | VoID file availability check for MediCare took 0.0006613731384277344s
Completeness | Calculation of interlinking completeness for MediCare took 0.27044081687927246s
Reputation | Calculation of the PageRank for MediCare took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for MediCare took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MediCare took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.029273986816406e-05s
Believability | Calculation of trust value for MediCare took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-medicare took 547.5249109268188s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 63.969589710235596s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0005593299865722656s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.6957554817199707s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.0210721492767334s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 0.00014543533325195312s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 78.39736151695251s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 5.721379518508911s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.29138803482055664s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.393692016601562e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 8.344650268554688e-06s
INFO | --- Analysis for fu-berlin-sider took 25.149930715560913s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 5.042398691177368s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0006241798400878906s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.23807597160339355s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.843971252441406e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.3589859008789062e-05s
INFO | --- Analysis for fu-berlin-stitch took 16.410229682922363s
Availability | SPARQL endpoint availability check for fvdb took 4.363059997558594e-05s
Availability | VoID file availability check for fvdb took 0.000518798828125s
Completeness | Calculation of interlinking completeness for fvdb took 0.2480771541595459s
Reputation | Calculation of the PageRank for fvdb took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for fvdb took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for fvdb took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.0279159545898438e-05s
Believability | Calculation of trust value for fvdb took 1.1682510375976562e-05s
INFO | --- Analysis for fv took 12.35988712310791s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.3392181396484375e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.00032901763916015625s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.24014639854431152s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.3855438232421875e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.3909759521484375e-06s
INFO | --- Analysis for GACS took 3.900424003601074s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.124641418457031e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.2647585868835449s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.8371810913085938e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 6.9141387939453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 3.369478225708008s
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.0006985664367675781s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.266521692276001s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.267692565917969e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 7.152557373046875e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 5.446479558944702s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.267692565917969e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.2698788642883301s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.918212890625e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 8.58306884765625e-06s
INFO | --- Analysis for garnicaplywood took 3.0884664058685303s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.410743713378906e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.000579833984375s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2820889949798584s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020531415939331055s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.250640869140625e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 6.9141387939453125e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.507598638534546s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.4023470878601074s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2565953731536865s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00010013580322265625s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for gemet took 5.044677257537842s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.220008850097656e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.25784969329833984s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.3855438232421875e-05s
Believability | Calculation of trust value for gemet-annotated took 1.0728836059570312e-05s
INFO | --- Analysis for gemet-annotated took 2.900341749191284s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7738280296325684s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.25505805015563965s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.933906555175781e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 5.7220458984375e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.159633159637451s
Availability | SPARQL endpoint availability check for Super Ontology took 0.9785935878753662s
Availability | VoID file availability check for Super Ontology took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2737092971801758s
Reputation | Calculation of the PageRank for Super Ontology took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Super Ontology took 7.62939453125e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 4.310866594314575s
Availability | SPARQL endpoint availability check for geo.place took 4.2438507080078125e-05s
Availability | VoID file availability check for geo.place took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for geo.place took 0.2817871570587158s
Reputation | Calculation of the PageRank for geo.place took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for geo.place took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.0279159545898438e-05s
Believability | Calculation of trust value for geo.place took 7.152557373046875e-06s
INFO | --- Analysis for geo_place took 2.9640376567840576s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.38690185546875e-05s
Availability | VoID file availability check for Geographic detector model took 0.0003407001495361328s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.2640376091003418s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.0279159545898438e-05s
Believability | Calculation of trust value for Geographic detector model took 7.152557373046875e-06s
INFO | --- Analysis for GeoDetector took 12.13614535331726s
Availability | SPARQL endpoint availability check for geodomainwn took 6.961822509765625e-05s
Availability | VoID file availability check for geodomainwn took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.24546241760253906s
Reputation | Calculation of the PageRank for geodomainwn took 0.021288394927978516s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0010051727294921875s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 7.081031799316406e-05s
Believability | Calculation of trust value for geodomainwn took 8.58306884765625e-06s
INFO | --- Analysis for geodomainwn took 6.57819676399231s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.410743713378906e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2971358299255371s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.866455078125e-05s
Believability | Calculation of trust value for GeoEcuador took 8.106231689453125e-06s
INFO | --- Analysis for geoecuador took 12.46591830253601s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2068793773651123s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006821155548095703s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.294539213180542s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.021672964096069336s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 7.128715515136719e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 6.4373016357421875e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.306153535842896s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.935264587402344e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.277238130569458s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020623445510864258s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.266334533691406e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.152557373046875e-06s
INFO | --- Analysis for geographic-openuplabs took 3.2935047149658203s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.8450124263763428s
Availability | VoID file availability check for GeoLinkedData took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.269057035446167s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.059906005859375e-05s
Believability | Calculation of trust value for GeoLinkedData took 5.245208740234375e-06s
INFO | --- Analysis for geolinkeddata took 4.32719612121582s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.26114344596862793s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0005323886871337891s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 10.873911380767822s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.40106821060180664s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.13841533660888672s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.303093671798706s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.19597554206848145s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.1692502498626709s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.18560314178466797s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.09367203712463379s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.09419608116149902s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.07027053833007812s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09550285339355469s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 2.125899076461792s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.0889439582824707s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.1013956069946289s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.13097071647644043s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09757232666015625s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.07783985137939453s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.0857706069946289s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.493936777114868s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.462501525878906e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.05878639221191406s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06182503700256348s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.0947415828704834s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.06621170043945312s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06244921684265137s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.2520873546600342s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.15921378135681152s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.571079969406128s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08986496925354004s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07587075233459473s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06164741516113281s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.31437182426452637s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.007594108581542969s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.23215532302856445s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.06983160972595215s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.2263321876525879s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5248441696166992s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 2.8379874229431152s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.3254632949829102s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.4817709922790527s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.17611479759216309s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.061036109924316406s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0268619060516357s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.34703755378723145s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.130073547363281e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.0728836059570312e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 76.65666913986206s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.315376281738281e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2740030288696289s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.00047588348388671875s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.152557373046875e-06s
INFO | --- Analysis for geonames-semantic-web took 4.053448438644409s
Availability | SPARQL endpoint availability check for Geospatial World  took 5.53131103515625e-05s
Availability | VoID file availability check for Geospatial World  took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2546980381011963s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00011134147644042969s
Believability | Calculation of trust value for Geospatial World  took 7.152557373046875e-06s
INFO | --- Analysis for geospatialworld-net took 2.971654176712036s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.5899758338928223s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.2882513999938965s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0008006095886230469s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00014734268188476562s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 6.67572021484375e-06s
INFO | --- Analysis for geospecies took 5.963921785354614s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.267692565917969e-05s
Availability | VoID file availability check for GeoWordNet took 0.0008101463317871094s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.27503299713134766s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.125999450683594e-05s
Believability | Calculation of trust value for GeoWordNet took 7.3909759521484375e-06s
INFO | --- Analysis for geowordnet took 7.557398557662964s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.0752859115600586s
Availability | VoID file availability check for German labor law thesaurus took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.26633715629577637s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02016592025756836s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.082389831542969e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.9188692569732666s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.282731294631958s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02021193504333496s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 3.886222839355469e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 7.867813110351562e-06s
INFO | --- Analysis for germlex took 2.7864584922790527s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.5083692073822021s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2519683837890625s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020384788513183594s
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.000751495361328125s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.131431579589844e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 7.152557373046875e-06s
INFO | --- Analysis for gesis-thesoz took 5.919489860534668s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.864657163619995s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.24608445167541504s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.414817810058594e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for getty-aat took 24.496370792388916s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 2.381075382232666s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.000652313232421875s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.26865720748901367s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.316734313964844e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 7.3909759521484375e-06s
INFO | --- Analysis for getty-tgn took 23.692145347595215s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.28112030029296875s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.27884888648986816s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.552436828613281e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 5.4836273193359375e-06s
INFO | --- Analysis for gipuzkoademografia took 2.8493950366973877s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.5299530029296875e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.27837228775024414s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.337860107421875e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 7.152557373046875e-06s
INFO | --- Analysis for glastonbury-2011 took 5.539693832397461s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.3392181396484375e-05s
Availability | VoID file availability check for Global Change Information System took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.25923609733581543s
Reputation | Calculation of the PageRank for Global Change Information System took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.3855438232421875e-05s
Believability | Calculation of trust value for Global Change Information System took 8.344650268554688e-06s
INFO | --- Analysis for global-change-information-system took 2.8834609985351562s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.982948303222656e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.2693657875061035s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020562410354614258s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.316734313964844e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 7.867813110351562e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.117696762084961s
Availability | SPARQL endpoint availability check for Glottolog took 4.3392181396484375e-05s
Availability | VoID file availability check for Glottolog took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2539193630218506s
Reputation | Calculation of the PageRank for Glottolog took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.125999450683594e-05s
Believability | Calculation of trust value for Glottolog took 5.9604644775390625e-06s
INFO | --- Analysis for glottolog took 7.221829891204834s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.5299530029296875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.26790595054626465s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00011014938354492188s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 7.62939453125e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 5.28846549987793s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.696846008300781e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.2524452209472656s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.0994415283203125e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 7.3909759521484375e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.915133237838745s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.220008850097656e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.2596099376678467s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.170967102050781e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 6.4373016357421875e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.9048712253570557s
Availability | SPARQL endpoint availability check for 1121 took 4.410743713378906e-05s
Availability | VoID file availability check for 1121 took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for 1121 took 0.2901012897491455s
Reputation | Calculation of the PageRank for 1121 took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 1121 took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.3855438232421875e-05s
Believability | Calculation of trust value for 1121 took 1.2636184692382812e-05s
INFO | --- Analysis for God_ took 3.337386131286621s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.363059997558594e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.27033352851867676s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.021124839782714844s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0008056163787841797s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.817413330078125e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 7.3909759521484375e-06s
INFO | --- Analysis for gold took 4.129319906234741s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 9.393692016601562e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0005545616149902344s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.266082763671875s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.271766662597656e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 6.4373016357421875e-06s
INFO | --- Analysis for googleart-wrapper took 2.8153164386749268s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.09658288955688477s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0007386207580566406s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2520935535430908s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.023087501525878906s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.00128173828125s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 5.125999450683594e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 7.867813110351562e-06s
INFO | --- Analysis for govagribus-denmark took 34.65985608100891s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.4696366786956787s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0004069805145263672s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.25507211685180664s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 8.797645568847656e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 23.96931004524231s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.5162103176116943s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0003952980041503906s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.23189997673034668s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.893013000488281e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 6.198883056640625e-06s
INFO | --- Analysis for govtrack took 9.859066247940063s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.482269287109375e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.2543473243713379s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02077507972717285s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.079673767089844e-05s
Believability | Calculation of trust value for greek-administrative-geography took 6.4373016357421875e-06s
INFO | --- Analysis for greek-administrative-geography took 4.168174743652344s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.6851387023925781s
Availability | VoID file availability check for Greek Wordnet took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.24890613555908203s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.1961669921875e-05s
Believability | Calculation of trust value for Greek Wordnet took 7.62939453125e-06s
INFO | --- Analysis for greek-wordnet took 3.0407509803771973s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 3.825493097305298s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0008955001831054688s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.25925493240356445s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.2636184692382812e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 7.62939453125e-06s
INFO | --- Analysis for greek_prisons_releases took 7.951390266418457s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.7814955711364746s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0003845691680908203s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2612752914428711s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020320892333984375s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 0.00011301040649414062s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.3909759521484375e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.4340736865997314s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.315376281738281e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0003075599670410156s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.23794126510620117s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02006983757019043s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.870529174804688e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 4.46220850944519s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 2.219703435897827s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.2724940776824951s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.02049875259399414s
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.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.839897155761719e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 5.9604644775390625e-06s
INFO | --- Analysis for grrp took 4.6862218379974365s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.5421702861785889s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.2432248592376709s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.818771362304688e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.0067901611328125e-06s
INFO | --- Analysis for grrt took 3.8982222080230713s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1105427742004395s
Availability | VoID file availability check for Geological Timescale took 0.0007562637329101562s
Extra | Recovery of all triples for Geological Timescale took 3.245307207107544s
Performance | Total latancy measurement for Geological Timescale took 5.046666622161865s
Amount of data | Number of triples check for Geological Timescale took 1.0738909244537354s
Interoperability | New terms check for Geological Timescale took 1.6713838577270508s
Versatility | Languages check for Geological Timescale took 1.7435290813446045s
Interpretability | Number of blank nodes check for Geological Timescale took 2.136620283126831s
Security | Check HTTPS for Geological Timescale took 0.36608028411865234s
Interpretability | RDF structures check for Geological Timescale took 0.4022350311279297s
Versatility | Serialization formats check for Geological Timescale took 1.1385722160339355s
Availability | RDF dump link check for Geological Timescale took 2.6763057708740234s
License | MR license check for Geological Timescale took 0.4169185161590576s
License | HR license check for Geological Timescale took 0.4839749336242676s
Amount of data | Number of property check for Geological Timescale took 1.0990266799926758s
Understandability | Number of label check for Geological Timescale took 0.472653865814209s
Understandability | URI regex check for Geological Timescale took 1.4947097301483154s
Understandability | Vocabs check for Geological Timescale took 0.4325401782989502s
Verifiability | Authors check for Geological Timescale took 0.41147613525390625s
Verifiability | Publishers check for Geological Timescale took 0.4425044059753418s
Performance | Throughput check for Geological Timescale took 18.516411781311035s
Amount of data | Check the number of entities for Geological Timescale took 0.0252530574798584s
Verifiability | Contribs. check for Geological Timescale took 1.0715787410736084s
Interlinking | sameAs chians check for Geological Timescale took 2.05452036857605s
Interlinking | skos check for Geological Timescale took 0.4900848865509033s
Interlinking | skos check for Geological Timescale took 1.0762157440185547s
Timeliness | dataset update frequency check for Geological Timescale took 0.42165112495422363s
Currency | Creation date check for Geological Timescale took 1.5177018642425537s
Currency | Modification date check for Geological Timescale took 1.0560245513916016s
Rep.Conc. | URIs length for Geological Timescale took 3.7552430629730225s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.39105224609375s
Accuracy | Check Functional Property for Geological Timescale took 1.0957763195037842s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.45658397674560547s
Accuracy | Check Empty annotation labels for Geological Timescale took 0.8271331787109375s
Accuracy | Check White space in annotation for Geological Timescale took 0.015829801559448242s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07454061508178711s
Consistency | Disjoint class check for Geological Timescale took 2.1164119243621826s
Consistency | Check Misplaced properties for Geological Timescale took 2.150911808013916s
Consistency | Misplaced classes for Geological Timescale took 0.5399467945098877s
Consistency | Check Ontology hijacking for Geological Timescale took 2.308892011642456s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.1301264762878418s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.2568318843841553s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05051231384277344s
Conciseness | Check Intensional conciseness for Geological Timescale took 1.1430788040161133s
Security | Sign check for Geological Timescale took 0.9798762798309326s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.799480676651001s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.33865952491760254s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.05718994140625e-05s
Believability | Calculation of trust value for Geological Timescale took 7.3909759521484375e-06s
INFO | --- Analysis for GTS took 150.90693831443787s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2820777893066406s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.695487976074219e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for GTS-ont took 2.5693395137786865s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.220008850097656e-05s
Availability | VoID file availability check for GUTSTOK  took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.6925692558288574s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 3.1948089599609375e-05s
Believability | Calculation of trust value for GUTSTOK  took 6.67572021484375e-06s
INFO | --- Analysis for Guillaume_Forget took 2.7605504989624023s
Availability | SPARQL endpoint availability check for Project Gutenberg took 5.5789947509765625e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0003757476806640625s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.24430203437805176s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.604194641113281e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.67572021484375e-06s
INFO | --- Analysis for gutenberg took 9.782174348831177s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 9.989738464355469e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007925033569335938s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.29285216331481934s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.528594970703125e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 5.9604644775390625e-06s
INFO | --- Analysis for gwa-ili took 5.681790828704834s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.363059997558594e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2859995365142822s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.0517578125e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 7.152557373046875e-06s
INFO | --- Analysis for GWR took 14.443063974380493s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.458427429199219e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.2557988166809082s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.02071213722229004s
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.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.147125244140625e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 5.9604644775390625e-06s
INFO | --- Analysis for HASM took 9.89464259147644s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.2438507080078125e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.26732897758483887s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.0994415283203125e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 6.4373016357421875e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.8443379402160645s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.494684934616089s
Availability | VoID file availability check for HealthCare Ontology took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.23982906341552734s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.021321773529052734s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.886222839355469e-05s
Believability | Calculation of trust value for HealthCare Ontology took 8.58306884765625e-06s
INFO | --- Analysis for HealthCare_Ontology took 6.23222541809082s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.3392181396484375e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.2548186779022217s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.021344423294067383s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0008189678192138672s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 8.177757263183594e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 6.67572021484375e-06s
INFO | --- Analysis for heartfailure took 2.647430181503296s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 22.26792573928833s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007579326629638672s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.2584567070007324s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020581483840942383s
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.811981201171875e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.6253204345703125e-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.4373016357421875e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 122.71285247802734s
Availability | SPARQL endpoint availability check for Hedatuz took 0.21998977661132812s
Availability | VoID file availability check for Hedatuz took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.2803778648376465s
Reputation | Calculation of the PageRank for Hedatuz took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.933906555175781e-05s
Believability | Calculation of trust value for Hedatuz took 8.58306884765625e-06s
INFO | --- Analysis for hedatuz took 2.9613559246063232s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.12923240661621094s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.26411986351013184s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012803077697753906s
Believability | Calculation of trust value for Hellenic Fire Brigade took 4.5299530029296875e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.5976390838623047s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.026224374771118164s
Availability | VoID file availability check for Hellenic Police took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.27129459381103516s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02050161361694336s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012826919555664062s
Believability | Calculation of trust value for Hellenic Police took 9.775161743164062e-06s
INFO | --- Analysis for hellenic-police took 2.4064981937408447s
Availability | SPARQL endpoint availability check for Hermos took 4.57763671875e-05s
Availability | VoID file availability check for Hermos took 0.0008618831634521484s
Completeness | Calculation of interlinking completeness for Hermos took 0.24611759185791016s
Reputation | Calculation of the PageRank for Hermos took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for Hermos took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hermos took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.0279159545898438e-05s
Believability | Calculation of trust value for Hermos took 7.3909759521484375e-06s
INFO | --- Analysis for Hermos took 3.0980310440063477s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.410743713378906e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2610812187194824s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020901203155517578s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 4.38690185546875e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 5.7220458984375e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.410940647125244s
Availability | SPARQL endpoint availability check for HITO took 0.4323241710662842s
Availability | VoID file availability check for HITO took 0.0005962848663330078s
Extra | Recovery of all triples for HITO took 3.11370587348938s
Performance | Total latancy measurement for HITO took 0.9910860061645508s
Amount of data | Number of triples check for HITO took 0.20152807235717773s
Interoperability | New terms check for HITO took 1.4024007320404053s
Versatility | Languages check for HITO took 0.2228085994720459s
Interpretability | Number of blank nodes check for HITO took 0.20652318000793457s
Interpretability | RDF structures check for HITO took 0.2003946304321289s
Versatility | Serialization formats check for HITO took 0.18618011474609375s
Availability | RDF dump link check for HITO took 0.20630741119384766s
License | MR license check for HITO took 0.19568991661071777s
License | HR license check for HITO took 0.20984530448913574s
Amount of data | Number of property check for HITO took 0.19707632064819336s
Understandability | Number of label check for HITO took 0.18754816055297852s
Understandability | URI regex check for HITO took 0.392470121383667s
Understandability | Vocabs check for HITO took 0.19649457931518555s
Verifiability | Authors check for HITO took 0.20820116996765137s
Verifiability | Publishers check for HITO took 0.18521523475646973s
Performance | Throughput check for HITO took 11.578960418701172s
Amount of data | Check the number of entities for HITO took 9.298324584960938e-05s
Verifiability | Contribs. check for HITO took 0.20269274711608887s
Interlinking | sameAs chians check for HITO took 0.18587636947631836s
Interlinking | skos check for HITO took 0.2079169750213623s
Interlinking | skos check for HITO took 0.19710516929626465s
Timeliness | dataset update frequency check for HITO took 0.18741083145141602s
Currency | Creation date check for HITO took 0.393113374710083s
Currency | Modification date check for HITO took 0.39436984062194824s
Rep.Conc. | URIs length for HITO took 1.2219552993774414s
Interoperability | New vocabularies check for HITO took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.18973827362060547s
Accuracy | Check Functional Property for HITO took 0.19672441482543945s
Accuracy | Check Inverse Functional Property for HITO took 0.18397259712219238s
Accuracy | Check Empty annotation labels for HITO took 0.5225231647491455s
Accuracy | Check White space in annotation for HITO took 0.01323080062866211s
Accuracy | Check Datatype consistency for HITO took 0.0714108943939209s
Consistency | Disjoint class check for HITO took 0.20837759971618652s
Consistency | Check Misplaced properties for HITO took 0.5323233604431152s
Consistency | Misplaced classes for HITO took 0.3491053581237793s
Consistency | Check Ontology hijacking for HITO took 1.630955696105957s
Consistency | Check Invalid usage of undefined classes for HITO took 1.180706262588501s
Consistency | Check Invalid usage of undefined properties for HITO took 1.4333906173706055s
Conciseness | Check Extensional conciseness for HITO took 0.06275343894958496s
Conciseness | Check Intensional conciseness for HITO took 0.20850396156311035s
Security | Sign check for HITO took 0.18365216255187988s
Availability | Check URIs Dereferenciability for HITO took 1658.1983165740967s
Completeness | Calculation of interlinking completeness for HITO took 1.5042424201965332s
Reputation | Calculation of the PageRank for HITO took 0.026988744735717773s
Interlinking | Calculation of Degree of Connection for HITO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for HITO took 8.225440979003906e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 3.0994415283203125e-06s
Believability | Calculation of trust value for HITO took 8.344650268554688e-06s
INFO | --- Analysis for hito took 1712.7162101268768s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 8.093083143234253s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.7038455009460449s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.218650817871094e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 6.4373016357421875e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 45.31068658828735s
Availability | SPARQL endpoint availability check for Homologene took 4.1484832763671875e-05s
Availability | VoID file availability check for Homologene took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Homologene took 0.7268364429473877s
Reputation | Calculation of the PageRank for Homologene took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for Homologene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Homologene took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.86102294921875e-05s
Believability | Calculation of trust value for Homologene took 7.62939453125e-06s
INFO | --- Analysis for homologene took 4.287775754928589s
Availability | SPARQL endpoint availability check for gseg took 4.291534423828125e-05s
Availability | VoID file availability check for gseg took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for gseg took 0.700110912322998s
Reputation | Calculation of the PageRank for gseg took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for gseg took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for gseg took 2.7894973754882812e-05s
Believability | Calculation of trust value for gseg took 6.4373016357421875e-06s
INFO | --- Analysis for hongse took 3.724015474319458s
Availability | SPARQL endpoint availability check for Noticias Universia took 5.53131103515625e-05s
Availability | VoID file availability check for Noticias Universia took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.25174856185913086s
Reputation | Calculation of the PageRank for Noticias Universia took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Noticias Universia took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 2.8371810913085938e-05s
Believability | Calculation of trust value for Noticias Universia took 7.152557373046875e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.8508646488189697s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.220008850097656e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2544517517089844s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 2.6941299438476562e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 6.67572021484375e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.892270088195801s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.8267569541931152s
Availability | VoID file availability check for COURAGE Dataset took 0.0006611347198486328s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.2523386478424072s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.765655517578125e-05s
Believability | Calculation of trust value for COURAGE Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.90151047706604s
Availability | SPARQL endpoint availability check for RoadTrb took 4.3392181396484375e-05s
Availability | VoID file availability check for RoadTrb took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.2919795513153076s
Reputation | Calculation of the PageRank for RoadTrb took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for RoadTrb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.7894973754882812e-05s
Believability | Calculation of trust value for RoadTrb took 7.152557373046875e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.466170072555542s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.9591064453125e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0008311271667480469s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2520143985748291s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 6.198883056640625e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 24.652890920639038s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.3392181396484375e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.24503087997436523s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.8848648071289062e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 5.7220458984375e-06s
INFO | --- Analysis for http:pakistan.com took 2.7467703819274902s
Availability | SPARQL endpoint availability check for CEDICT took 4.601478576660156e-05s
Availability | VoID file availability check for CEDICT took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for CEDICT took 0.2677476406097412s
Reputation | Calculation of the PageRank for CEDICT took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for CEDICT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CEDICT took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CEDICT took 2.8848648071289062e-05s
Believability | Calculation of trust value for CEDICT took 5.9604644775390625e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.423816919326782s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.050232172012329s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2577967643737793s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020339250564575195s
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.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.914138793945312e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 11.266871690750122s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.124641418457031e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.27863097190856934s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 2.8371810913085938e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 6.4373016357421875e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.848938226699829s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.315376281738281e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.00034880638122558594s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.2507491111755371s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.02010655403137207s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 2.86102294921875e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 6.198883056640625e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.7254176139831543s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Soccer Dataset took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.26587605476379395s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020186185836791992s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Soccer Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for http:www.msm.com took 2.364804267883301s
Availability | SPARQL endpoint availability check for Game Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Game Ontology took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.24437236785888672s
Reputation | Calculation of the PageRank for Game Ontology took 0.020374774932861328s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007958412170410156s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.8848648071289062e-05s
Believability | Calculation of trust value for Game Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.8947408199310303s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.291534423828125e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2566385269165039s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0251998901367188e-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.0279159545898438e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 6.198883056640625e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.362478017807007s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.649162292480469e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.27967000007629395s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007169246673583984s
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 5.245208740234375e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.3376054763793945s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.220008850097656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.25556111335754395s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02009296417236328s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7894973754882812e-05s
Believability | Calculation of trust value for Indian Biodiversity took 5.4836273193359375e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.3260345458984375s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.220008850097656e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.23858165740966797s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.198883056640625e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.321169376373291s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.221366882324219e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2573821544647217s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007166862487792969s
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:bioportal.bioontology.orgontologiesIBIOp=summary took 2.3448235988616943s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.7206878662109375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0007476806640625s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2693345546722412s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021838665008544922s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.337860107421875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 8.344650268554688e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.737088918685913s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.649162292480469e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.000324249267578125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2417919635772705s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0994415283203125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2874603271484375e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.3432116508483887s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.3392181396484375e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.24845242500305176s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.7894973754882812e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 5.9604644775390625e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 3.8526999950408936s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1497466564178467s
Availability | VoID file availability check for Bookkeeping took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.2536327838897705s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bookkeeping took 5.9604644775390625e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.9686715602874756s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Legal Ontology took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.26581406593322754s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020249128341674805s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.218650817871094e-05s
Believability | Calculation of trust value for Legal Ontology took 8.106231689453125e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.892956495285034s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.7206878662109375e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.25023627281188965s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.343292236328125e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.152557373046875e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.6193745136260986s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.3392181396484375e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.2642791271209717s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.8133392333984375e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 6.198883056640625e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.514892578125s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.076957702636719e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.25334835052490234s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 2.8133392333984375e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 1.1920928955078125e-05s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.846808671951294s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.100799560546875e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2664060592651367s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020168781280517578s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 2.86102294921875e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 6.198883056640625e-06s
INFO | --- Analysis for hud-library-usagedata took 2.8666703701019287s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.6265780925750732s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.2591269016265869s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.02028632164001465s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010371208190917969s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.0013580322265625e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 4.386767148971558s
Availability | SPARQL endpoint availability check for IATE RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for IATE RDF took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.269329309463501s
Reputation | Calculation of the PageRank for IATE RDF took 0.020789146423339844s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.62396240234375e-05s
Believability | Calculation of trust value for IATE RDF took 7.62939453125e-06s
INFO | --- Analysis for iate-rdf took 2.524000883102417s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 0.638739824295044s
Availability | VoID file availability check for IATI as Linked Data took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.2599020004272461s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.535385131835938e-05s
Believability | Calculation of trust value for IATI as Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for iati-as-linked-data took 7.767178297042847s
Availability | SPARQL endpoint availability check for ICANE took 0.4013829231262207s
Availability | VoID file availability check for ICANE took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for ICANE took 0.2435605525970459s
Reputation | Calculation of the PageRank for ICANE took 0.020200014114379883s
Interlinking | Calculation of Degree of Connection for ICANE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICANE took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.416175842285156e-05s
Believability | Calculation of trust value for ICANE took 8.106231689453125e-06s
INFO | --- Analysis for icane took 3.7970893383026123s
Availability | SPARQL endpoint availability check for ichoose took 0.15091657638549805s
Availability | VoID file availability check for ichoose took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for ichoose took 0.2522754669189453s
Reputation | Calculation of the PageRank for ichoose took 0.02104663848876953s
Interlinking | Calculation of Degree of Connection for ichoose took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.794929504394531e-05s
Believability | Calculation of trust value for ichoose took 8.58306884765625e-06s
INFO | --- Analysis for ichoose took 44.27303433418274s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.5024416446685791s
Availability | VoID file availability check for The Iconology Dataset took 0.0006356239318847656s
Extra | Recovery of all triples for The Iconology Dataset took 4.980386257171631s
Performance | Total latancy measurement for The Iconology Dataset took 0.5013046264648438s
Amount of data | Number of triples check for The Iconology Dataset took 0.1779956817626953s
Interoperability | New terms check for The Iconology Dataset took 1.3460721969604492s
Versatility | Languages check for The Iconology Dataset took 0.5422873497009277s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.22194337844848633s
Interpretability | RDF structures check for The Iconology Dataset took 0.11104822158813477s
Versatility | Serialization formats check for The Iconology Dataset took 0.09954047203063965s
Availability | RDF dump link check for The Iconology Dataset took 0.09265780448913574s
License | MR license check for The Iconology Dataset took 0.10009574890136719s
License | HR license check for The Iconology Dataset took 0.2924158573150635s
Amount of data | Number of property check for The Iconology Dataset took 0.09890937805175781s
Understandability | Number of label check for The Iconology Dataset took 0.14377903938293457s
Understandability | URI regex check for The Iconology Dataset took 0.1691751480102539s
Understandability | Vocabs check for The Iconology Dataset took 0.09282350540161133s
Verifiability | Authors check for The Iconology Dataset took 0.0990297794342041s
Verifiability | Publishers check for The Iconology Dataset took 0.08941221237182617s
Performance | Throughput check for The Iconology Dataset took 10.436668634414673s
Amount of data | Check the number of entities for The Iconology Dataset took 0.00016379356384277344s
Verifiability | Contribs. check for The Iconology Dataset took 0.09358692169189453s
Interlinking | sameAs chians check for The Iconology Dataset took 0.09094786643981934s
Interlinking | skos check for The Iconology Dataset took 0.0953977108001709s
Interlinking | skos check for The Iconology Dataset took 0.08819842338562012s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.09265637397766113s
Currency | Creation date check for The Iconology Dataset took 0.1875767707824707s
Currency | Modification date check for The Iconology Dataset took 0.19776153564453125s
Rep.Conc. | URIs length for The Iconology Dataset took 1.3872261047363281s
Interoperability | New vocabularies check for The Iconology Dataset took 5.9604644775390625e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08193397521972656s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2371833324432373s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016649961471557617s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.4503457546234131s
Consistency | Disjoint class check for The Iconology Dataset took 0.07099127769470215s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.15075230598449707s
Consistency | Misplaced classes for The Iconology Dataset took 0.8945798873901367s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.5168328285217285s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.1807782649993896s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.2559616565704346s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.29930925369262695s
Security | Sign check for The Iconology Dataset took 0.08285236358642578s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2552.7229018211365s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.2073478698730469s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 2.0742416381835938e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for The Iconology Dataset took 7.62939453125e-06s
INFO | --- Analysis for iconology-dataset took 2612.381268978119s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.172325134277344e-05s
Availability | VoID file availability check for Identifiers.org took 0.0004024505615234375s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.27417707443237305s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.838539123535156e-05s
Believability | Calculation of trust value for Identifiers.org took 7.62939453125e-06s
INFO | --- Analysis for identifiers-org took 4.3335840702056885s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.315376281738281e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.28099703788757324s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.748603820800781e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 6.9141387939453125e-06s
INFO | --- Analysis for idreffr took 4.367224454879761s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.9255740642547607s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.28607702255249023s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02018260955810547s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.673004150390625e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 5.4836273193359375e-06s
INFO | --- Analysis for ids took 4.755381345748901s
Availability | SPARQL endpoint availability check for ietflang took 4.2438507080078125e-05s
Availability | VoID file availability check for ietflang took 0.0006496906280517578s
Completeness | Calculation of interlinking completeness for ietflang took 0.24379205703735352s
Reputation | Calculation of the PageRank for ietflang took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for ietflang took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.4345855712890625e-05s
Believability | Calculation of trust value for ietflang took 7.152557373046875e-06s
INFO | --- Analysis for ietflang took 12.549503087997437s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.464846134185791s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.2831590175628662s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02024698257446289s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for IGVLL took 4.480093955993652s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.43759894371032715s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0005934238433837891s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.9309017658233643s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9651479721069336s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.20692157745361328s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.3408966064453125s
Versatility | Languages check for 3LGM² IHE Ontology took 0.20047688484191895s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.19422268867492676s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.19521474838256836s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.20760750770568848s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.18357133865356445s
License | MR license check for 3LGM² IHE Ontology took 0.19533634185791016s
License | HR license check for 3LGM² IHE Ontology took 0.21126604080200195s
Amount of data | Number of property check for 3LGM² IHE Ontology took 0.19632792472839355s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.20874428749084473s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.3777751922607422s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.1951296329498291s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.18444156646728516s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.1841447353363037s
Performance | Throughput check for 3LGM² IHE Ontology took 11.396484851837158s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 8.440017700195312e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.1843400001525879s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.19537687301635742s
Interlinking | skos check for 3LGM² IHE Ontology took 0.19588446617126465s
Interlinking | skos check for 3LGM² IHE Ontology took 0.2070450782775879s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.2074906826019287s
Currency | Creation date check for 3LGM² IHE Ontology took 0.40365099906921387s
Currency | Modification date check for 3LGM² IHE Ontology took 0.36881351470947266s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8554556369781494s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.18371987342834473s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.19964098930358887s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.2015082836151123s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3298976421356201s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0017621517181396484s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.05236458778381348s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.18353867530822754s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.44998931884765625s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.28150415420532227s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.5059771537780762s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.1331756114959717s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.4009127616882324s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.03118896484375s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.20868778228759766s
Security | Sign check for 3LGM² IHE Ontology took 0.19768309593200684s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 408.84056878089905s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.8419139385223389s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.1920928955078125e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 8.106231689453125e-06s
INFO | --- Analysis for IHE took 455.29591965675354s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.04072403907775879s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.2708745002746582s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020256519317626953s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.0013580322265625e-05s
INFO | --- Analysis for iislod-test took 4.717075824737549s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.315376281738281e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2632265090942383s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007417201995849609s
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 8.106231689453125e-06s
INFO | --- Analysis for ILUSOC took 15.610534429550171s
Availability | SPARQL endpoint availability check for im@sparql took 6.469517946243286s
Availability | VoID file availability check for im@sparql took 0.0006275177001953125s
Completeness | Calculation of interlinking completeness for im@sparql took 0.2783522605895996s
Reputation | Calculation of the PageRank for im@sparql took 0.020661592483520508s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0011248588562011719s
Interlinking | Calculation of Clustering coefficient for im@sparql took 3.910064697265625e-05s
Believability | Calculation of trust value for im@sparql took 7.3909759521484375e-06s
INFO | --- Analysis for im@sparql took 13.465723991394043s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.2438507080078125e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2854321002960205s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020258188247680664s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 3.1948089599609375e-05s
Believability | Calculation of trust value for imagery bailingniao took 6.67572021484375e-06s
INFO | --- Analysis for imagery_bailingniao took 4.021579742431641s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.208369255065918s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0006172657012939453s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 22.434950828552246s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.9475648403167725s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.74439525604248s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.2982211112976074s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.815798997879028s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.696443557739258s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7657124996185303s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7988109588623047s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7929105758666992s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7894158363342285s
License | MR license check for Imagesnippets Image Descriptions took 0.8076136112213135s
License | HR license check for Imagesnippets Image Descriptions took 10.784749746322632s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.8213396072387695s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.7880728244781494s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.5930814743041992s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7948713302612305s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7925693988800049s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.7900588512420654s
Performance | Throughput check for Imagesnippets Image Descriptions took 15.340438842773438s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 6.0558319091796875e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.8158614635467529s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.7695286273956299s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.8179996013641357s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.7923471927642822s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.8408961296081543s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.6160085201263428s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.5791332721710205s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 31.816975355148315s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7888619899749756s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7973213195800781s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.94596266746521s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7986741065979004s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.826236248016357s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 17.70812153816223s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 8.21511459350586s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00015497207641601562s
Security | Sign check for Imagesnippets Image Descriptions took 0.8188788890838623s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.7000410556793213s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.989738464355469e-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 265.4025683403015s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.9707002639770508s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.2605404853820801s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.083747863769531e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 6.198883056640625e-06s
INFO | --- Analysis for imf-linked-data took 5.296718597412109s
Availability | SPARQL endpoint availability check for IMGpedia took 8.320808410644531e-05s
Availability | VoID file availability check for IMGpedia took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2518727779388428s
Reputation | Calculation of the PageRank for IMGpedia took 0.020809173583984375s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.266334533691406e-05s
Believability | Calculation of trust value for IMGpedia took 7.867813110351562e-06s
INFO | --- Analysis for imgpedia took 2.916609525680542s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.4345855712890625e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.25080227851867676s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.02039933204650879s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 3.0279159545898438e-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.6974122524261475s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 6.127357482910156e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0003154277801513672s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2653343677520752s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1682510375976562e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 5.9604644775390625e-06s
INFO | --- Analysis for Imtiaz took 2.378009796142578s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.4345855712890625e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2677481174468994s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 3.0994415283203125e-05s
Believability | Calculation of trust value for Royalty Free Music took 5.0067901611328125e-06s
INFO | --- Analysis for inaudio.org took 3.408107042312622s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.220008850097656e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.25866007804870605s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.0994415283203125e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 4.1961669921875e-05s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.868293285369873s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.1484832763671875e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.28455162048339844s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.647804260253906e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 7.867813110351562e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.936617612838745s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.3753621578216553s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006024837493896484s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.25586938858032227s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.7670135498046875e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 5.9604644775390625e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 3.931004762649536s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.220008850097656e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.24496936798095703s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.1948089599609375e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 6.67572021484375e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 3.434008836746216s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 8.726119995117188e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0005784034729003906s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2647545337677002s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.02052164077758789s
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.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.0001068115234375s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 6.67572021484375e-06s
INFO | --- Analysis for ineverycrea took 19.671340703964233s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.38690185546875e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2849295139312744s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00010657310485839844s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 5.0067901611328125e-06s
INFO | --- Analysis for ineverycrea-argentina took 12.235764503479004s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 523.5784428119659s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2887918949127197s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 8.845329284667969e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for influence-tracker-dataset took 1080.8192784786224s
Availability | SPARQL endpoint availability check for INSEMTIVES took 5.507469177246094e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.7039237022399902s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 8.344650268554688e-05s
Believability | Calculation of trust value for INSEMTIVES took 7.152557373046875e-06s
INFO | --- Analysis for insemtives took 6.673044443130493s
Availability | SPARQL endpoint availability check for instagram.person took 4.100799560546875e-05s
Availability | VoID file availability check for instagram.person took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for instagram.person took 0.26567649841308594s
Reputation | Calculation of the PageRank for instagram.person took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for instagram.person took 2.9087066650390625e-05s
Believability | Calculation of trust value for instagram.person took 1.2636184692382812e-05s
INFO | --- Analysis for instagram_person took 4.677847385406494s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.1484832763671875e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.28304100036621094s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020377159118652344s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.8133392333984375e-05s
Believability | Calculation of trust value for instagram.videoobject took 7.3909759521484375e-06s
INFO | --- Analysis for instagram_videoobject took 3.4266467094421387s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.029273986816406e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2530100345611572s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub Countries took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-countries took 2.879866361618042s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 5.626678466796875e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2568831443786621s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020427227020263672s
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.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8371810913085938e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.3322043418884277s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.2589073181152344s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 2.7894973754882812e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-organizations took 3.341887950897217s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub People took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.24068379402160645s
Reputation | Calculation of the PageRank for Instance Hub People took 0.020345211029052734s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.4332275390625e-05s
Believability | Calculation of trust value for Instance Hub People took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-people took 2.8087172508239746s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 5.269050598144531e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.2571744918823242s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.9802322387695312e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.8399882316589355s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.267692565917969e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.25101757049560547s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 1.049041748046875e-05s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.7886199951171875s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 5.245208740234375e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2555994987487793s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 2.7894973754882812e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 3.3289167881011963s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 3.981590270996094e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.29599666595458984s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 8.821487426757812e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.9306423664093018s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.315376281738281e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.25311946868896484s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.8498754501342773s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.6253204345703125e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.2487640380859375s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 2.8848648071289062e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 6.4373016357421875e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.8024814128875732s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.26890087127685547s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02014470100402832s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.855938673019409s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.1484832763671875e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.25463104248046875s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.02037191390991211s
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.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 2.8848648071289062e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 7.62939453125e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.8669025897979736s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006344318389892578s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.24560880661010742s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010633468627929688s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for interactivemaps-gnoss took 8.892735481262207s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.1484832763671875e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.27817606925964355s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.02216362953186035s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.170967102050781e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 6.9141387939453125e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.8584537506103516s
Availability | SPARQL endpoint availability check for intervalue took 0.7432408332824707s
Availability | VoID file availability check for intervalue took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for intervalue took 0.24541711807250977s
Reputation | Calculation of the PageRank for intervalue took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for intervalue took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for intervalue took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.532669067382812e-05s
Believability | Calculation of trust value for intervalue took 6.67572021484375e-06s
INFO | --- Analysis for intervalue took 3.1367807388305664s
Availability | SPARQL endpoint availability check for Inztrow took 4.1961669921875e-05s
Availability | VoID file availability check for Inztrow took 0.0006494522094726562s
Completeness | Calculation of interlinking completeness for Inztrow took 0.25441408157348633s
Reputation | Calculation of the PageRank for Inztrow took 0.020114660263061523s
Interlinking | Calculation of Degree of Connection for Inztrow took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Inztrow took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.9325485229492188e-05s
Believability | Calculation of trust value for Inztrow took 6.9141387939453125e-06s
INFO | --- Analysis for Inztrow took 5.108934640884399s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0010242462158203125s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.26152801513671875s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 8.106231689453125e-06s
INFO | --- Analysis for ipbes took 3.973381280899048s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.363059997558594e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0007264614105224609s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.266033411026001s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02026224136352539s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.38690185546875e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 7.3909759521484375e-06s
INFO | --- Analysis for iptc-newscodes took 3.3034145832061768s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.1484832763671875e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.2653329372406006s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.0279159545898438e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 6.67572021484375e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.9133191108703613s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.484835624694824s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.00041413307189941406s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.24558520317077637s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0009720325469970703s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 0.00011086463928222656s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.3909759521484375e-06s
INFO | --- Analysis for iserve took 9.087860584259033s
Availability | SPARQL endpoint availability check for ISIC V4 took 20.793651819229126s
Availability | VoID file availability check for ISIC V4 took 0.0009131431579589844s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2587110996246338s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 4.673004150390625e-05s
Believability | Calculation of trust value for ISIC V4 took 5.7220458984375e-06s
INFO | --- Analysis for isic-v4 took 115.71839499473572s
Availability | SPARQL endpoint availability check for Isidore took 4.172325134277344e-05s
Availability | VoID file availability check for Isidore took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Isidore took 0.2398378849029541s
Reputation | Calculation of the PageRank for Isidore took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for Isidore took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Isidore took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.0040740966796875e-05s
Believability | Calculation of trust value for Isidore took 6.9141387939453125e-06s
INFO | --- Analysis for isidore took 2.9382336139678955s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.38690185546875e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0006415843963623047s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2512516975402832s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020593881607055664s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.224082946777344e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 4.76837158203125e-06s
INFO | --- Analysis for isil-dbpedia took 4.503302097320557s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.1961669921875e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.2634735107421875s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 6.9141387939453125e-06s
INFO | --- Analysis for iso-3166-2-data took 2.913987398147583s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.291534423828125e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.26000356674194336s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02045440673828125s
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.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.552436828613281e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 7.3909759521484375e-06s
INFO | --- Analysis for iso-639-oasis took 3.685370683670044s
Availability | SPARQL endpoint availability check for ISOcat took 4.124641418457031e-05s
Availability | VoID file availability check for ISOcat took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for ISOcat took 0.26226377487182617s
Reputation | Calculation of the PageRank for ISOcat took 0.020441532135009766s
Interlinking | Calculation of Degree of Connection for ISOcat took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for ISOcat took 6.580352783203125e-05s
Believability | Calculation of trust value for ISOcat took 7.152557373046875e-06s
INFO | --- Analysis for isocat took 33.0929491519928s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 7.843971252441406e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0006160736083984375s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.24840903282165527s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.504753112792969e-05s
Believability | Calculation of trust value for ISOcat-metadata took 6.9141387939453125e-06s
INFO | --- Analysis for isocat-metadata took 5.051408767700195s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.124641418457031e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.26698946952819824s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 2.9087066650390625e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 6.67572021484375e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.9637632369995117s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3650217056274414s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0005888938903808594s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.032349348068237s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7063114643096924s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21505093574523926s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 2.935126304626465s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.89876103401184s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18523597717285156s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.12068819999694824s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2006371021270752s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1528768539428711s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16336345672607422s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24847197532653809s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.96433305740356s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1566932201385498s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.4059569835662842s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4962790012359619s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.24398231506347656s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.23664546012878418s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1403946876525879s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.512728452682495s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00018072128295898438s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21168160438537598s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2601144313812256s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4639701843261719s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.4559473991394043s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.19612765312194824s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.3198986053466797s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15209269523620605s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.106289625167847s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17008543014526367s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.14251041412353516s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15824508666992188s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.27798318862915s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.311678409576416s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29718828201293945s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1332688331604004s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.671407699584961s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.018054723739624s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.122152090072632s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1700987815856934s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.857869625091553s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.29255199432373047s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21768450736999512s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18949460983276367s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.382008790969849s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3789036273956299s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.822845458984375e-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 8.106231689453125e-06s
INFO | --- Analysis for ispra-lod-place took 464.8874399662018s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.6253204345703125e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0003294944763183594s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.2596745491027832s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.075599670410156e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 6.9141387939453125e-06s
INFO | --- Analysis for ispra-lod-rmn took 5.068224906921387s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.14513373374938965s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0005688667297363281s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 8.059449195861816s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.912785530090332s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.2178177833557129s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 2.9029595851898193s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.60460925102234s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.21425819396972656s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.11190938949584961s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.1872420310974121s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.17384052276611328s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.14241552352905273s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.2737104892730713s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 90.35697937011719s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.2038109302520752s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.4531974792480469s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.5179624557495117s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.23603248596191406s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.21919655799865723s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.17598557472229004s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.584961891174316s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.43865966796875e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.22438263893127441s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.2743833065032959s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.47321224212646484s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.4863169193267822s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.236741304397583s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3469996452331543s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.13938212394714355s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.478572607040405s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.1491105556488037s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15338420867919922s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.16425561904907227s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 4.761329174041748s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3134911060333252s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.28555989265441895s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.1445930004119873s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.750840425491333s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.982839822769165s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.092386722564697s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.208850383758545s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.866178274154663s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2904839515686035s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.15706324577331543s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.19376373291015625s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.78715705871582s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.8396029472351074s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020737648010253906s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.24249267578125e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.430511474609375e-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 463.37433671951294s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.1484832763671875e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.25535011291503906s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 2.9087066650390625e-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.7008957862854004s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.6915266513824463s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0003349781036376953s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2469184398651123s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.274482727050781e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 6.67572021484375e-06s
INFO | --- Analysis for issa-agritrop took 5.791709899902344s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.410743713378906e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.7367808818817139s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.9087066650390625e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.867813110351562e-06s
INFO | --- Analysis for ISSN:0080-3626 took 3.2915656566619873s
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.0005393028259277344s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.25028252601623535s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02010178565979004s
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.0007832050323486328s
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 7.152557373046875e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 2.7664639949798584s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.267692565917969e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.25908732414245605s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020229578018188477s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 2.9325485229492188e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 5.9604644775390625e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.550440549850464s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 2.1432528495788574s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.26308655738830566s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007224082946777344s
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.4836273193359375e-06s
INFO | --- Analysis for istat-immigration took 4.576070547103882s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.029273986816406e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.26103997230529785s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.0040740966796875e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 6.9141387939453125e-06s
INFO | --- Analysis for istat-immigrazione took 2.824786901473999s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.46433329582214355s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.3010108470916748s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.956390380859375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 4.291534423828125e-06s
INFO | --- Analysis for it-aifa-drug-prices took 3.5467023849487305s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.544414758682251s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0003771781921386719s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.261951208114624s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.343292236328125e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 6.9141387939453125e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.965439558029175s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.267692565917969e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.26494789123535156s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020270824432373047s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007779598236083984s
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 7.152557373046875e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.881643056869507s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.172325134277344e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.24463868141174316s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.020191669464111328s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.0279159545898438e-05s
Believability | Calculation of trust value for IWMI Research Reports took 7.867813110351562e-06s
INFO | --- Analysis for iwmi-research-reports took 2.835527181625366s
Availability | SPARQL endpoint availability check for IWN took 4.363059997558594e-05s
Availability | VoID file availability check for IWN took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for IWN took 0.25656843185424805s
Reputation | Calculation of the PageRank for IWN took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for IWN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IWN took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for IWN took 3.647804260253906e-05s
Believability | Calculation of trust value for IWN took 6.9141387939453125e-06s
INFO | --- Analysis for iwn took 2.7377660274505615s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.1961669921875e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.26079297065734863s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.020392894744873047s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 2.8848648071289062e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 1.2636184692382812e-05s
INFO | --- Analysis for j-global-knowledge took 2.820089101791382s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.267692565917969e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.23949003219604492s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020193815231323242s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.0040740966796875e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 8.106231689453125e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.912815809249878s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.222845554351807s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.29033398628234863s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.628036499023438e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.0967254638671875e-05s
INFO | --- Analysis for jamendo-dbtune took 25.331440448760986s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.458427429199219e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.25479912757873535s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.76837158203125e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 4.5299530029296875e-06s
INFO | --- Analysis for japan-radioactivity-stat took 4.388762950897217s
Availability | SPARQL endpoint availability check for JEL Classification took 4.291534423828125e-05s
Availability | VoID file availability check for JEL Classification took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.24130821228027344s
Reputation | Calculation of the PageRank for JEL Classification took 0.026791095733642578s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.814697265625e-05s
Believability | Calculation of trust value for JEL Classification took 8.821487426757812e-06s
INFO | --- Analysis for jel-classification took 42.69633650779724s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 0.3997611999511719s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2631344795227051s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.02033233642578125s
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.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 7.152557373046875e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 5.753518104553223s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.72449374198914s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.2591056823730469s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020698070526123047s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.796287536621094e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 7.62939453125e-06s
INFO | --- Analysis for jita took 540.5389180183411s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 6.580352783203125e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.25432324409484863s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.552436828613281e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 1.1920928955078125e-05s
INFO | --- Analysis for jmdict took 6.1544349193573s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.074775218963623s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006706714630126953s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.2795412540435791s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02070140838623047s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 0.000102996826171875s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.152557373046875e-06s
INFO | --- Analysis for john-goodwins-family-tree took 63.61526656150818s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.172325134277344e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.27062249183654785s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.24249267578125e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 6.67572021484375e-06s
INFO | --- Analysis for jp-cos took 4.947912931442261s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.363059997558594e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.2571899890899658s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.02040839195251465s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.838539123535156e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 6.4373016357421875e-06s
INFO | --- Analysis for jp-textbook took 5.195716857910156s
Availability | SPARQL endpoint availability check for JRC-Names took 4.291534423828125e-05s
Availability | VoID file availability check for JRC-Names took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.26950740814208984s
Reputation | Calculation of the PageRank for JRC-Names took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for JRC-Names took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for JRC-Names took 0.0009989738464355469s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.886222839355469e-05s
Believability | Calculation of trust value for JRC-Names took 1.0728836059570312e-05s
INFO | --- Analysis for jrc-names-ec took 4.742938041687012s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 1.0511705875396729s
Availability | VoID file availability check for JRC-Names-MLODE took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2497236728668213s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 7.295608520507812e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 6.9141387939453125e-06s
INFO | --- Analysis for jrc-names-mlode took 4.397886753082275s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.267692565917969e-05s
Availability | VoID file availability check for JudaicaLink took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2559943199157715s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010704994201660156s
Believability | Calculation of trust value for JudaicaLink took 7.867813110351562e-06s
INFO | --- Analysis for judaicalink took 4.588589191436768s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.1961669921875e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.26012635231018066s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.4332275390625e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 7.152557373046875e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.977198839187622s
Availability | SPARQL endpoint availability check for KAKEN took 5.650520324707031e-05s
Availability | VoID file availability check for KAKEN took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for KAKEN took 0.2584197521209717s
Reputation | Calculation of the PageRank for KAKEN took 0.020794153213500977s
Interlinking | Calculation of Degree of Connection for KAKEN took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for KAKEN took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.361701965332031e-05s
Believability | Calculation of trust value for KAKEN took 9.775161743164062e-06s
INFO | --- Analysis for kaken took 2.908478021621704s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07828640937805176s
Availability | VoID file availability check for Kallikratis municipalities took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2762775421142578s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.021090269088745117s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.679794311523438e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.9604644775390625e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.522751569747925s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.172325134277344e-05s
Availability | VoID file availability check for Openflights Routes took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.24979019165039062s
Reputation | Calculation of the PageRank for Openflights Routes took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.170967102050781e-05s
Believability | Calculation of trust value for Openflights Routes took 1.6689300537109375e-05s
INFO | --- Analysis for kasabi-openflights-routes took 2.8385441303253174s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.291534423828125e-05s
Availability | VoID file availability check for EU Soccer League took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2946772575378418s
Reputation | Calculation of the PageRank for EU Soccer League took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.528594970703125e-05s
Believability | Calculation of trust value for EU Soccer League took 5.9604644775390625e-06s
INFO | --- Analysis for KG:Course_Submission took 4.656804323196411s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 5.364418029785156e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.2567870616912842s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.239776611328125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 5.4836273193359375e-06s
INFO | --- Analysis for KING took 2.598909378051758s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.863739013671875e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0006594657897949219s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.2582986354827881s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.771087646484375e-05s
Believability | Calculation of trust value for Klappstuhlclub took 5.0067901611328125e-06s
INFO | --- Analysis for klappstuhlclub took 12.519737720489502s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.920714139938354s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.2611565589904785s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.793571472167969e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 6.67572021484375e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.413580417633057s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.124641418457031e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.23926186561584473s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020360231399536133s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0994415283203125e-05s
Believability | Calculation of trust value for Knowledge Forest took 6.9141387939453125e-06s
INFO | --- Analysis for knowledge-map took 2.829310655593872s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.363059997558594e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.2661099433898926s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.86102294921875e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.152557373046875e-06s
INFO | --- Analysis for KnowledgeFusion took 2.321718454360962s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.363059997558594e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.2716553211212158s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.747245788574219e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 6.198883056640625e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.224517822265625s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.220008850097656e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.2709031105041504s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.24249267578125e-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.89689040184021s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.982948303222656e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.26602935791015625s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020215272903442383s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.9087066650390625e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0728836059570312e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.315688371658325s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.2438507080078125e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.2489931583404541s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.02072596549987793s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 3.814697265625e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 6.4373016357421875e-06s
INFO | --- Analysis for ktr took 2.8698675632476807s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.410743713378906e-05s
Availability | VoID file availability check for Informatics Studies took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.2501187324523926s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 3.0994415283203125e-05s
Believability | Calculation of trust value for Informatics Studies took 6.198883056640625e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.7781596183776855s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.08185672760009766s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.5483560562133789s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2625298500061035s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.719329833984375e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 6.198883056640625e-06s
INFO | --- Analysis for kupkb took 8.158076524734497s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.2438507080078125e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.25603795051574707s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 3.0279159545898438e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 6.67572021484375e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.9062654972076416s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.18842077255249s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2857213020324707s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.021019697189331055s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0008575916290283203s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 9.679794311523438e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.62939453125e-06s
INFO | --- Analysis for l3s-dblp took 49.59875416755676s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 25.253111124038696s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.26647400856018066s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.842613220214844e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for lak-dataset took 68.22618556022644s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.33745408058166504s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005578994750976562s
Extra | Recovery of all triples for  Language Name Authority List  took 77.43331265449524s
Performance | Total latancy measurement for  Language Name Authority List  took 0.6148169040679932s
Amount of data | Number of triples check for  Language Name Authority List  took 97.35315561294556s
Interoperability | New terms check for  Language Name Authority List  took 91.03789925575256s
Versatility | Languages check for  Language Name Authority List  took 300.0617907047272s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 1.2086520195007324s
Security | Check HTTPS for  Language Name Authority List  took 0.37050819396972656s
Interpretability | RDF structures check for  Language Name Authority List  took 0.6451451778411865s
Versatility | Serialization formats check for  Language Name Authority List  took 3.813398599624634s
Availability | RDF dump link check for  Language Name Authority List  took 0.29912495613098145s
License | MR license check for  Language Name Authority List  took 0.14326953887939453s
License | HR license check for  Language Name Authority List  took 300.0515019893646s
Amount of data | Number of property check for  Language Name Authority List  took 0.19869780540466309s
Understandability | Number of label check for  Language Name Authority List  took 6.6974499225616455s
Understandability | URI regex check for  Language Name Authority List  took 0.26021695137023926s
Understandability | Vocabs check for  Language Name Authority List  took 0.10460424423217773s
Verifiability | Authors check for  Language Name Authority List  took 0.10019040107727051s
Verifiability | Publishers check for  Language Name Authority List  took 0.2530481815338135s
Performance | Throughput check for  Language Name Authority List  took 10.61605954170227s
Amount of data | Check the number of entities for  Language Name Authority List  took 7.081031799316406e-05s
Verifiability | Contribs. check for  Language Name Authority List  took 0.2055370807647705s
Interlinking | sameAs chians check for  Language Name Authority List  took 10.386964559555054s
Interlinking | skos check for  Language Name Authority List  took 0.5259716510772705s
Interlinking | skos check for  Language Name Authority List  took 0.24779939651489258s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.26805639266967773s
Currency | Creation date check for  Language Name Authority List  took 0.5073635578155518s
Currency | Modification date check for  Language Name Authority List  took 0.18603849411010742s
Rep.Conc. | URIs length for  Language Name Authority List  took 561.3676540851593s
Interoperability | New vocabularies check for  Language Name Authority List  took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.17192792892456055s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.16115117073059082s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.15749382972717285s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 26.76978611946106s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.205660104751587s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.643071413040161s
Consistency | Disjoint class check for  Language Name Authority List  took 0.13407468795776367s
Consistency | Check Misplaced properties for  Language Name Authority List  took 300.4002938270569s
Consistency | Misplaced classes for  Language Name Authority List  took 8.683603048324585s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 37.73731708526611s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.5621354579925537s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 301.4052951335907s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.0157065391540527s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.5788567066192627s
Security | Sign check for  Language Name Authority List  took 0.1396620273590088s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 4.163870811462402s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 1.5625083446502686s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.02116847038269043s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007939338684082031s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.369850158691406e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 2.1457672119140625e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 7.3909759521484375e-06s
INFO | --- Analysis for language-authority-list took 14799.345052957535s
Availability | SPARQL endpoint availability check for Lark took 385.0109210014343s
Availability | VoID file availability check for Lark took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Lark took 0.47879695892333984s
Reputation | Calculation of the PageRank for Lark took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Lark took 6.508827209472656e-05s
Interlinking | Calculation of Centrality for Lark took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Lark took 0.00012969970703125s
Believability | Calculation of trust value for Lark took 7.152557373046875e-06s
INFO | --- Analysis for LARK took 1678.569394826889s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.3943748474121094s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.7673256397247314s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020293474197387695s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.291534423828125e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LASLA took 6.297892093658447s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.2438507080078125e-05s
Availability | VoID file availability check for LATC Linksets took 0.00037169456481933594s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.25542449951171875s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.0040740966796875e-05s
Believability | Calculation of trust value for LATC Linksets took 7.62939453125e-06s
INFO | --- Analysis for latc-linksets took 3.7013461589813232s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.38114023208618164s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0003523826599121094s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.26007819175720215s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 4.649162292480469e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 4.210699796676636s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.34722185134887695s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.00041294097900390625s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.2423567771911621s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020252466201782227s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for LatinAffectus took 4.224139928817749s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.3490285873413086s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.26686835289001465s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.2438507080078125e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LatinWordnetLiLa took 3.774200916290283s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.2438507080078125e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.26906752586364746s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.02065300941467285s
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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.170967102050781e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 6.67572021484375e-06s
INFO | --- Analysis for lcc took 2.9052398204803467s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.410743713378906e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2705354690551758s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011849403381347656s
Believability | Calculation of trust value for Library of Congress Subject Headings took 7.62939453125e-06s
INFO | --- Analysis for lcsh took 6.010751962661743s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.38690185546875e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.2451639175415039s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020701885223388672s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.869171142578125e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.867813110351562e-06s
INFO | --- Analysis for lcsubjects took 3.032325506210327s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.267692565917969e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.24992728233337402s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 4.267692565917969e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 6.9141387939453125e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.923205614089966s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 9.400075197219849s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.25955915451049805s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 5.245208740234375e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 6.4373016357421875e-06s
INFO | --- Analysis for ldt@library took 37.53767704963684s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.7206878662109375e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.25379490852355957s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.147125244140625e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 9.059906005859375e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.9683096408843994s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 5.054473876953125e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.26351451873779297s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02086663246154785s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.1948089599609375e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 6.9141387939453125e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.8775928020477295s
Availability | SPARQL endpoint availability check for U ime Legije took 4.363059997558594e-05s
Availability | VoID file availability check for U ime Legije took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.2788701057434082s
Reputation | Calculation of the PageRank for U ime Legije took 0.020662307739257812s
Interlinking | Calculation of Degree of Connection for U ime Legije took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.170967102050781e-05s
Believability | Calculation of trust value for U ime Legije took 5.7220458984375e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.3434858322143555s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 7.414817810058594e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.246673583984375s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.0994415283203125e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 1.1682510375976562e-05s
INFO | --- Analysis for legislation-openuplabs took 2.8926429748535156s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.3465144634246826s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0006172657012939453s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.27204227447509766s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020641326904296875s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.43865966796875e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 8.58306884765625e-06s
INFO | --- Analysis for LemmaBank took 4.1791205406188965s
Availability | SPARQL endpoint availability check for lemonUby took 4.935264587402344e-05s
Availability | VoID file availability check for lemonUby took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for lemonUby took 0.24971938133239746s
Reputation | Calculation of the PageRank for lemonUby took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.437301635742188e-05s
Believability | Calculation of trust value for lemonUby took 6.67572021484375e-06s
INFO | --- Analysis for lemonuby took 3.129030704498291s
Availability | SPARQL endpoint availability check for LemonWiktionary took 4.291534423828125e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0011906623840332031s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2434384822845459s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02081298828125s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.933906555175781e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.62939453125e-06s
INFO | --- Analysis for lemonwiktionary took 4.120537757873535s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.35425829887390137s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0008327960968017578s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2738468647003174s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02074718475341797s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 5.9604644775390625e-06s
INFO | --- Analysis for LewisShort took 3.63242769241333s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.0793476104736328s
Availability | VoID file availability check for LEXIN-RDF took 0.0005879402160644531s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.26946282386779785s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.0517578125e-05s
Believability | Calculation of trust value for LEXIN-RDF took 6.67572021484375e-06s
INFO | --- Analysis for lexin-rdf took 5.505036115646362s
Availability | SPARQL endpoint availability check for lexinfo took 4.291534423828125e-05s
Availability | VoID file availability check for lexinfo took 0.0004112720489501953s
Completeness | Calculation of interlinking completeness for lexinfo took 0.26180076599121094s
Reputation | Calculation of the PageRank for lexinfo took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for lexinfo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for lexinfo took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.940696716308594e-05s
Believability | Calculation of trust value for lexinfo took 7.3909759521484375e-06s
INFO | --- Analysis for lexinfo took 2.7969071865081787s
Availability | SPARQL endpoint availability check for Lexvo took 7.176399230957031e-05s
Availability | VoID file availability check for Lexvo took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Lexvo took 0.2672860622406006s
Reputation | Calculation of the PageRank for Lexvo took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for Lexvo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lexvo took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017952919006347656s
Believability | Calculation of trust value for Lexvo took 1.1444091796875e-05s
INFO | --- Analysis for lexvo took 3.052245855331421s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.315376281738281e-05s
Availability | VoID file availability check for Lexvo.org took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.2547154426574707s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.390975952148438e-05s
Believability | Calculation of trust value for Lexvo.org took 5.9604644775390625e-06s
INFO | --- Analysis for lexvo-org took 2.472566843032837s
Availability | SPARQL endpoint availability check for LIBRIS took 0.35546278953552246s
Availability | VoID file availability check for LIBRIS took 0.0013494491577148438s
Extra | Recovery of all triples for LIBRIS took 18.014036893844604s
Performance | Total latancy measurement for LIBRIS took 0.67405104637146s
Amount of data | Number of triples check for LIBRIS took 21.371663808822632s
Interoperability | New terms check for LIBRIS took 15.490641832351685s
Versatility | Languages check for LIBRIS took 0.18060731887817383s
Interpretability | Number of blank nodes check for LIBRIS took 300.0954599380493s
Security | Check HTTPS for LIBRIS took 0.3646540641784668s
Interpretability | RDF structures check for LIBRIS took 0.23737430572509766s
Versatility | Serialization formats check for LIBRIS took 0.21697139739990234s
Availability | RDF dump link check for LIBRIS took 0.1319570541381836s
License | MR license check for LIBRIS took 0.21799373626708984s
License | HR license check for LIBRIS took 0.1784195899963379s
Amount of data | Number of property check for LIBRIS took 0.17653894424438477s
Understandability | Number of label check for LIBRIS took 0.38886308670043945s
Understandability | URI regex check for LIBRIS took 0.30249929428100586s
Understandability | Vocabs check for LIBRIS took 0.14931011199951172s
Verifiability | Authors check for LIBRIS took 0.15319323539733887s
Verifiability | Publishers check for LIBRIS took 0.13799142837524414s
Performance | Throughput check for LIBRIS took 10.547990798950195s
Amount of data | Check the number of entities for LIBRIS took 7.43865966796875e-05s
Verifiability | Contribs. check for LIBRIS took 0.1525585651397705s
Interlinking | sameAs chians check for LIBRIS took 0.16154098510742188s
Interlinking | skos check for LIBRIS took 0.20901727676391602s
Interlinking | skos check for LIBRIS took 0.13636350631713867s
Timeliness | dataset update frequency check for LIBRIS took 0.15047073364257812s
Currency | Creation date check for LIBRIS took 0.311077356338501s
Currency | Modification date check for LIBRIS took 0.5654454231262207s
Rep.Conc. | URIs length for LIBRIS took 85.20099115371704s
Interoperability | New vocabularies check for LIBRIS took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.17671561241149902s
Accuracy | Check Functional Property for LIBRIS took 0.18038439750671387s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.1331005096435547s
Accuracy | Check Datatype consistency for LIBRIS took 0.27795958518981934s
Consistency | Disjoint class check for LIBRIS took 0.21314525604248047s
Consistency | Check Misplaced properties for LIBRIS took 62.74467754364014s
Consistency | Misplaced classes for LIBRIS took 1.1485698223114014s
Consistency | Check Ontology hijacking for LIBRIS took 6.507826089859009s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.1521732807159424s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 63.42334842681885s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2815580368041992s
Conciseness | Check Intensional conciseness for LIBRIS took 0.3811511993408203s
Security | Sign check for LIBRIS took 0.24825143814086914s
Availability | Check URIs Dereferenciability for LIBRIS took 9.792967319488525s
Completeness | Calculation of interlinking completeness for LIBRIS took 1.242173671722412s
Reputation | Calculation of the PageRank for LIBRIS took 0.02004384994506836s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0008361339569091797s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 0.00010061264038085938s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 7.152557373046875e-06s
INFO | --- Analysis for libris took 1078.2967910766602s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.0640556812286377s
Availability | VoID file availability check for Public Library of Veroia took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.6912894248962402s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.486343383789062e-05s
Believability | Calculation of trust value for Public Library of Veroia took 7.152557373046875e-06s
INFO | --- Analysis for libver took 5.64323616027832s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.1788501739501953s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.239027738571167s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02113795280456543s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 8.392333984375e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.9604644775390625e-06s
INFO | --- Analysis for lichfield-spending took 3.0287411212921143s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.76837158203125e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.0007050037384033203s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.2651479244232178s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020479440689086914s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.7881393432617188e-05s
INFO | --- Analysis for lime took 6.864996671676636s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.506111145019531e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.30199241638183594s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00012731552124023438s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.62939453125e-06s
INFO | --- Analysis for lingvoj took 8.39380693435669s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2692117691040039s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.821487426757812e-05s
Believability | Calculation of trust value for Linked Crunchbase took 6.198883056640625e-06s
INFO | --- Analysis for linked-crunchbase took 2.7552430629730225s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.273253440856934s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0012669563293457031s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2463390827178955s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.200241088867188e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 5.7220458984375e-06s
INFO | --- Analysis for linked-drugs took 24.35723567008972s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 5.7697296142578125e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.2646973133087158s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020493030548095703s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.584426879882812e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 4.76837158203125e-06s
INFO | --- Analysis for linked-edgar took 4.418569803237915s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.482269287109375e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.25919389724731445s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.870529174804688e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.0728836059570312e-05s
INFO | --- Analysis for linked-eurostat took 3.392683267593384s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.458427429199219e-05s
Availability | VoID file availability check for linked hypernyms took 0.00061798095703125s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.30993056297302246s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0008890628814697266s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 8.559226989746094e-05s
Believability | Calculation of trust value for linked hypernyms took 8.344650268554688e-06s
INFO | --- Analysis for linked-hypernyms took 3.581653118133545s
Availability | SPARQL endpoint availability check for Linked Life Data took 192.54594373703003s
Availability | VoID file availability check for Linked Life Data took 0.0007252693176269531s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.6090593338012695s
Reputation | Calculation of the PageRank for Linked Life Data took 0.021373987197875977s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 5.6743621826171875e-05s
Believability | Calculation of trust value for Linked Life Data took 6.4373016357421875e-06s
INFO | --- Analysis for linked-life-data took 623.0595591068268s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.41769862174987793s
Availability | VoID file availability check for Linked Logainm took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.6711742877960205s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.081031799316406e-05s
Believability | Calculation of trust value for Linked Logainm took 7.3909759521484375e-06s
INFO | --- Analysis for linked-logainm took 5.555490970611572s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked NUTS took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.27084779739379883s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.030632019042969e-05s
Believability | Calculation of trust value for Linked NUTS took 5.0067901611328125e-06s
INFO | --- Analysis for linked-nuts took 2.947892189025879s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.363059997558594e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.25116562843322754s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020750761032104492s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 7.867813110351562e-06s
INFO | --- Analysis for linked-open-aalto-data-service took 2.889782428741455s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.7369933128356934s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0005214214324951172s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.26449131965637207s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020660400390625s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.814697265625e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for linked-open-camera took 4.607264041900635s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 6.496187448501587s
Availability | VoID file availability check for Linked Open Commerce took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.2854349613189697s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0517578125e-05s
Believability | Calculation of trust value for Linked Open Commerce took 7.867813110351562e-06s
INFO | --- Analysis for linked-open-commerce took 16.17206859588623s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 1.642960548400879s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.24556303024291992s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.02017068862915039s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.000102996826171875s
Believability | Calculation of trust value for Linked Open Data of Ecology took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 4.119581937789917s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.27150797843933105s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.012222290039062e-05s
Believability | Calculation of trust value for Linked Open Numbers took 7.62939453125e-06s
INFO | --- Analysis for linked-open-numbers took 2.498884677886963s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.410743713378906e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2589445114135742s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.02020430564880371s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.8133392333984375e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.7220458984375e-06s
INFO | --- Analysis for linked-open-piracy took 6.1041951179504395s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2637600898742676s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 7.867813110351562e-06s
INFO | --- Analysis for linked-open-senate took 2.92808198928833s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 12.522568941116333s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.25334906578063965s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.744529724121094e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 5.9604644775390625e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 50.09699845314026s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.25435566902160645s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020230770111083984s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.3855438232421875e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 4.291534423828125e-06s
INFO | --- Analysis for linked-periodicals took 2.52638578414917s
Availability | SPARQL endpoint availability check for Linked Index took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Index took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Linked Index took 0.28411173820495605s
Reputation | Calculation of the PageRank for Linked Index took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.296966552734375e-05s
Believability | Calculation of trust value for Linked Index took 6.9141387939453125e-06s
INFO | --- Analysis for linked-stockindex took 2.3372535705566406s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 5.225388526916504s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2703518867492676s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.0231170654296875s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0021686553955078125s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 8.153915405273438e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 7.3909759521484375e-06s
INFO | --- Analysis for linked-structured-product-labels took 13.352112770080566s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.7164449691772461s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.26149868965148926s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.147125244140625e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 3.600120544433594e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 3.270761251449585s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.170490741729736s
Availability | VoID file availability check for Linked TCGA took 0.0007534027099609375s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.2596156597137451s
Reputation | Calculation of the PageRank for Linked TCGA took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.7738037109375e-05s
Believability | Calculation of trust value for Linked TCGA took 7.152557373046875e-06s
INFO | --- Analysis for linked-tcga took 62.68893051147461s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.23071050643920898s
Availability | VoID file availability check for Linked User Feedback took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.30768823623657227s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.9577484130859375e-05s
Believability | Calculation of trust value for Linked User Feedback took 8.344650268554688e-06s
INFO | --- Analysis for linked-user-feedback took 2.6092450618743896s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.6253204345703125e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0007190704345703125s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2793617248535156s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020615100860595703s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.915496826171875e-05s
Believability | Calculation of trust value for USPTO Patent data took 8.344650268554688e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.50838541984558s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.506111145019531e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2758309841156006s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 7.867813110351562e-06s
INFO | --- Analysis for linked-web-apis took 2.910336494445801s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.2438507080078125e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.2936241626739502s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.361701965332031e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 9.059906005859375e-06s
INFO | --- Analysis for linkedarc took 2.898249387741089s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.06665992736816406s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.26997900009155273s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020884037017822266s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.528594970703125e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 7.3909759521484375e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.747356653213501s
Availability | SPARQL endpoint availability check for LinkedCT took 1.5477492809295654s
Availability | VoID file availability check for LinkedCT took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.25611138343811035s
Reputation | Calculation of the PageRank for LinkedCT took 0.02033400535583496s
Interlinking | Calculation of Degree of Connection for LinkedCT took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.965896606445312e-05s
Believability | Calculation of trust value for LinkedCT took 5.4836273193359375e-06s
INFO | --- Analysis for linkedct took 5.198512554168701s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.2861924171447754s
Availability | VoID file availability check for LinkedGeoData took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.2520146369934082s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.02030491828918457s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00011682510375976562s
Believability | Calculation of trust value for LinkedGeoData took 5.9604644775390625e-06s
INFO | --- Analysis for linkedgeodata took 2.9562485218048096s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 4.100799560546875e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.28388428688049316s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.02096390724182129s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.4809112548828125e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 7.3909759521484375e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 2.9814860820770264s
Availability | SPARQL endpoint availability check for LinkedLCCN took 10.072540044784546s
Availability | VoID file availability check for LinkedLCCN took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.25998759269714355s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00011944770812988281s
Believability | Calculation of trust value for LinkedLCCN took 6.67572021484375e-06s
INFO | --- Analysis for linkedlccn took 28.2962863445282s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.5299530029296875e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2693965435028076s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020740032196044922s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.7670135498046875e-05s
Believability | Calculation of trust value for LinkedMarkMail took 6.4373016357421875e-06s
INFO | --- Analysis for linkedmarkmail took 2.600461959838867s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.816333532333374s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007510185241699219s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2372887134552002s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013947486877441406s
Believability | Calculation of trust value for Linked Movie DataBase took 1.1444091796875e-05s
INFO | --- Analysis for linkedmdb took 133.5444746017456s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.23447751998901367s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.2577207088470459s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.653236389160156e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 5.7220458984375e-06s
INFO | --- Analysis for linkedspending took 2.91444993019104s
Availability | SPARQL endpoint availability check for LinkedStats took 4.315376281738281e-05s
Availability | VoID file availability check for LinkedStats took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2625150680541992s
Reputation | Calculation of the PageRank for LinkedStats took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 2.9087066650390625e-05s
Believability | Calculation of trust value for LinkedStats took 6.67572021484375e-06s
INFO | --- Analysis for linkedstats took 2.877995014190674s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.38690185546875e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2591252326965332s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 2.8371810913085938e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 6.9141387939453125e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.911020278930664s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.291534423828125e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.24864864349365234s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 1.2159347534179688e-05s
INFO | --- Analysis for linking-open-drug-data took 2.890946865081787s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.045291900634765625s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.2550535202026367s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010514259338378906s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 5.4836273193359375e-06s
INFO | --- Analysis for linklion took 2.4533655643463135s
Availability | SPARQL endpoint availability check for Lion's Den took 4.124641418457031e-05s
Availability | VoID file availability check for Lion's Den took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.26924824714660645s
Reputation | Calculation of the PageRank for Lion's Den took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 2.8371810913085938e-05s
Believability | Calculation of trust value for Lion's Den took 6.67572021484375e-06s
INFO | --- Analysis for lionsden took 2.9063143730163574s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 33.59763050079346s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2821013927459717s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020716428756713867s
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.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 6.0558319091796875e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 40.13671660423279s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.220008850097656e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.28095293045043945s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020729541778564453s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.170967102050781e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.152557373046875e-06s
INFO | --- Analysis for livtdm took 2.9044382572174072s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.3392181396484375e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.241715669631958s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02115321159362793s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.266334533691406e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 7.152557373046875e-06s
INFO | --- Analysis for livtdm2017 took 2.856917142868042s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.2438507080078125e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.25589680671691895s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020769357681274414s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.218650817871094e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 6.9141387939453125e-06s
INFO | --- Analysis for lobi took 2.926959753036499s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.0977702140808105s
Availability | VoID file availability check for lobid-organisations took 0.0005657672882080078s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.26727819442749023s
Reputation | Calculation of the PageRank for lobid-organisations took 0.021000146865844727s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.846687316894531e-05s
Believability | Calculation of trust value for lobid-organisations took 8.821487426757812e-06s
INFO | --- Analysis for lobid-organisations took 5.7411208152771s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.9000270366668701s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.253248929977417s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.0001010894775390625s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.3909759521484375e-06s
INFO | --- Analysis for lobid-resources took 7.985352277755737s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.410743713378906e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.2564125061035156s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.748603820800781e-05s
Believability | Calculation of trust value for Linked Open Colors took 6.9141387939453125e-06s
INFO | --- Analysis for loc took 7.443680047988892s
Availability | SPARQL endpoint availability check for Location Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Location Ontology took 0.0006749629974365234s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.2791574001312256s
Reputation | Calculation of the PageRank for Location Ontology took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for Location Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for Location_Ontology took 3.5184929370880127s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.649162292480469e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0006198883056640625s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.26366710662841797s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.147125244140625e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 6.4373016357421875e-06s
INFO | --- Analysis for locv took 33.03833556175232s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7721455097198486s
Availability | VoID file availability check for LOD-a-lot took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2668898105621338s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020536422729492188s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.956390380859375e-05s
Believability | Calculation of trust value for LOD-a-lot took 6.9141387939453125e-06s
INFO | --- Analysis for lod-a-lot took 13.912126541137695s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 6.771087646484375e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.25913286209106445s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 1.3828277587890625e-05s
INFO | --- Analysis for lod-it_scuole-italiane took 2.919541835784912s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.1961669921875e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.2571103572845459s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.9325485229492188e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 7.3909759521484375e-06s
INFO | --- Analysis for lod-taiwan took 2.845268964767456s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.267692565917969e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0011365413665771484s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.248260498046875s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.916854858398438e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 9.059906005859375e-06s
INFO | --- Analysis for lod2-project-wiki took 3.856968641281128s
Availability | SPARQL endpoint availability check for LODAC BDLS took 3.1547811031341553s
Availability | VoID file availability check for LODAC BDLS took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2599318027496338s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0008594989776611328s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 8.821487426757812e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.152557373046875e-06s
INFO | --- Analysis for lodac-bdls took 14.12991189956665s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.1484832763671875e-05s
Availability | VoID file availability check for LODRussia Math took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.24584269523620605s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.86102294921875e-05s
Believability | Calculation of trust value for LODRussia Math took 8.106231689453125e-06s
INFO | --- Analysis for lodrussia-math took 2.8710649013519287s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.482269287109375e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.26137638092041016s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.9087066650390625e-05s
Believability | Calculation of trust value for LODRussia Nano took 7.62939453125e-06s
INFO | --- Analysis for lodrussia-nano took 2.8949027061462402s
Availability | SPARQL endpoint availability check for LODStats took 4.6253204345703125e-05s
Availability | VoID file availability check for LODStats took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for LODStats took 0.2629866600036621s
Reputation | Calculation of the PageRank for LODStats took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for LODStats took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LODStats took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.6941299438476562e-05s
Believability | Calculation of trust value for LODStats took 6.9141387939453125e-06s
INFO | --- Analysis for lodstats took 2.9218227863311768s
Availability | SPARQL endpoint availability check for LODUM took 5.221366882324219e-05s
Availability | VoID file availability check for LODUM took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for LODUM took 0.2800142765045166s
Reputation | Calculation of the PageRank for LODUM took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for LODUM took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LODUM took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.0040740966796875e-05s
Believability | Calculation of trust value for LODUM took 7.3909759521484375e-06s
INFO | --- Analysis for lodum took 2.9794397354125977s
Availability | SPARQL endpoint availability check for lofd took 0.1394023895263672s
Availability | VoID file availability check for lofd took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for lofd took 0.2548036575317383s
Reputation | Calculation of the PageRank for lofd took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for lofd took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for lofd took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for lofd took 2.9087066650390625e-05s
Believability | Calculation of trust value for lofd took 7.152557373046875e-06s
INFO | --- Analysis for lofd took 2.4836463928222656s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 271.66359543800354s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.31622862815856934s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.021283626556396484s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.984306335449219e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 9.5367431640625e-06s
INFO | --- Analysis for loius took 585.7686369419098s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.601478576660156e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.29613161087036133s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.7418136596679688e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.62939453125e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 6.15446662902832s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 2.030181884765625s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.0009763240814208984s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.282970666885376s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.030632019042969e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 5.0067901611328125e-06s
INFO | --- Analysis for london-gazette took 7.939983129501343s
Availability | SPARQL endpoint availability check for Weather Stations took 4.2438507080078125e-05s
Availability | VoID file availability check for Weather Stations took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2584521770477295s
Reputation | Calculation of the PageRank for Weather Stations took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Weather Stations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 7.987022399902344e-05s
Believability | Calculation of trust value for Weather Stations took 6.198883056640625e-06s
INFO | --- Analysis for los_metar took 4.220032453536987s
Availability | SPARQL endpoint availability check for Lotico took 0.8199479579925537s
Availability | VoID file availability check for Lotico took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Lotico took 0.2557682991027832s
Reputation | Calculation of the PageRank for Lotico took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for Lotico took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lotico took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.678436279296875e-05s
Believability | Calculation of trust value for Lotico took 5.9604644775390625e-06s
INFO | --- Analysis for lotico took 6.276809930801392s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 0.36835169792175293s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.27134037017822266s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02020716667175293s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.0517578125e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.0728836059570312e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 3.8751296997070312s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6129424571990967s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0002472400665283203s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 119.38749599456787s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.98610520362854s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.084773778915405s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 13.773366212844849s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2139413356781s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.004682779312134s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.26491785049438477s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.490840435028076s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2591843605041504s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.48656415939331055s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.2551498413086s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3240976333618164s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.3021652698516846s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.59912109375s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.29164791107177734s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1905205249786377s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2582371234893799s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.355918884277344s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 7.152557373046875e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21396136283874512s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20381665229797363s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5527570247650146s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4446432590484619s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.430988073348999s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.49704909324645996s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22376418113708496s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 153.5585834980011s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21066689491271973s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3176612854003906s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.34178805351257324s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 42.444581747055054s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.722491979598999s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.710777997970581s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19015932083129883s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 81.6109311580658s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.251358985900879s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 35.89955735206604s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.2645835876464844s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 89.60072231292725s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.729912519454956s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.596895694732666s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6225926876068115s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.341360330581665s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.4487509727478027s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.021188735961914062s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.2901763916015625e-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 7.62939453125e-06s
INFO | --- Analysis for LPIS_(Poland) took 2270.6950118541718s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1925821304321289s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00026535987854003906s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 114.48868751525879s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9339878559112549s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.159440279006958s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 12.99028205871582s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.18513917922974s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.8403327465057373s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22162961959838867s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 9.28763723373413s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.23500657081604004s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3406829833984375s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.21517157554626s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.32422924041748047s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.484055995941162s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.638723611831665s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2691984176635742s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22251248359680176s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2682979106903076s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.709510803222656s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.581710815429688e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2137155532836914s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21277594566345215s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.47752976417541504s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.45369863510131836s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.3667285442352295s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5045382976531982s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.22461819648742676s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 157.61613178253174s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21098709106445312s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3874974250793457s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2434091567993164s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.14854431152344s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7279794216156006s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6560747623443604s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20099902153015137s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 83.60753917694092s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.532233953475952s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 36.3265061378479s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.2300047874450684s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 84.93301439285278s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7711410522460938s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5062093734741211s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5291688442230225s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 10.229593753814697s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.4836163520812988s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02173614501953125s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2263.052304506302s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.315376281738281e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.2522571086883545s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.02107858657836914s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.695487976074219e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 8.106231689453125e-06s
INFO | --- Analysis for lremap-auth took 28.401761293411255s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.482269287109375e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2639894485473633s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 2.8848648071289062e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 6.4373016357421875e-06s
INFO | --- Analysis for lremap-conf took 16.073668241500854s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.601478576660156e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0007824897766113281s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.2837333679199219s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020890474319458008s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.147125244140625e-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.285213232040405s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.506111145019531e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.26380300521850586s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02080845832824707s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.170967102050781e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 7.62939453125e-06s
INFO | --- Analysis for lremap-sub took 13.583796262741089s
Availability | SPARQL endpoint availability check for LSQ took 4.458427429199219e-05s
Availability | VoID file availability check for LSQ took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for LSQ took 0.2936830520629883s
Reputation | Calculation of the PageRank for LSQ took 0.023543119430541992s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.361701965332031e-05s
Believability | Calculation of trust value for LSQ took 7.867813110351562e-06s
INFO | --- Analysis for lsq took 3.385255813598633s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.4888191223144531s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.27158403396606445s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for LucaniPharsalia took 4.313992023468018s
Availability | SPARQL endpoint availability check for Linked rules took 4.744529724121094e-05s
Availability | VoID file availability check for Linked rules took 0.0004055500030517578s
Completeness | Calculation of interlinking completeness for Linked rules took 0.2701539993286133s
Reputation | Calculation of the PageRank for Linked rules took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for Linked rules took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked rules took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Linked rules took 5.507469177246094e-05s
Believability | Calculation of trust value for Linked rules took 7.867813110351562e-06s
INFO | --- Analysis for Luminaires_senlis took 2.3564484119415283s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.5299530029296875e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.27546143531799316s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.03122854232788086s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0012066364288330078s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 4.029273986816406e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 6.9141387939453125e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.893784761428833s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.35384202003479s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2702782154083252s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020618200302124023s
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.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.933906555175781e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.62939453125e-06s
INFO | --- Analysis for makg took 63.47605657577515s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.3392181396484375e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.30792665481567383s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020396947860717773s
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.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.814697265625e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 6.9141387939453125e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.6065995693206787s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.315376281738281e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.25266408920288086s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020364046096801758s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.867813110351562e-06s
INFO | --- Analysis for manish took 3.266871929168701s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.291534423828125e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.26364803314208984s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.147125244140625e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 5.4836273193359375e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.860637664794922s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.3392181396484375e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.2685580253601074s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.314018249511719e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 5.9604644775390625e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 3.2735044956207275s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.38690185546875e-05s
Availability | VoID file availability check for MARC Codes List took 0.0007586479187011719s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.26662278175354004s
Reputation | Calculation of the PageRank for MARC Codes List took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.0001251697540283203s
Believability | Calculation of trust value for MARC Codes List took 7.3909759521484375e-06s
INFO | --- Analysis for marc-codes took 14.066216468811035s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.6253204345703125e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.6848948001861572s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.673004150390625e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.4373016357421875e-06s
INFO | --- Analysis for masc took 80.07580852508545s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.267692565917969e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.265993595123291s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020675182342529297s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.9577484130859375e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 7.152557373046875e-06s
INFO | --- Analysis for masc-bn-nif took 2.8326621055603027s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.8050081729888916s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.27870917320251465s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0008134841918945312s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.4332275390625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 6.9141387939453125e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.838360071182251s
Availability | SPARQL endpoint availability check for medline took 6.222724914550781e-05s
Availability | VoID file availability check for medline took 0.0013375282287597656s
Completeness | Calculation of interlinking completeness for medline took 0.24892473220825195s
Reputation | Calculation of the PageRank for medline took 0.021506071090698242s
Interlinking | Calculation of Degree of Connection for medline took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for medline took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for medline took 3.7670135498046875e-05s
Believability | Calculation of trust value for medline took 7.3909759521484375e-06s
INFO | --- Analysis for medline took 7.4419920444488525s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 1.5564332008361816s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.26108670234680176s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.414817810058594e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.867813110351562e-06s
INFO | --- Analysis for meducator took 15.461419820785522s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.2438507080078125e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.26776599884033203s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.600120544433594e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 6.198883056640625e-06s
INFO | --- Analysis for mesh-finnish took 2.886941432952881s
Availability | SPARQL endpoint availability check for MeSH headings took 4.267692565917969e-05s
Availability | VoID file availability check for MeSH headings took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.26593899726867676s
Reputation | Calculation of the PageRank for MeSH headings took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.0517578125e-05s
Believability | Calculation of trust value for MeSH headings took 6.4373016357421875e-06s
INFO | --- Analysis for mesh_headings took 2.938852548599243s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.363059997558594e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.26285576820373535s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.020596027374267578s
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.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.170967102050781e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.152557373046875e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.8531320095062256s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.1484832763671875e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2577967643737793s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.86102294921875e-05s
Believability | Calculation of trust value for MeSH pairs took 5.7220458984375e-06s
INFO | --- Analysis for mesh_pairs took 2.9195942878723145s
Availability | SPARQL endpoint availability check for MeSH titles took 4.2438507080078125e-05s
Availability | VoID file availability check for MeSH titles took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.25257372856140137s
Reputation | Calculation of the PageRank for MeSH titles took 0.020846128463745117s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 3.24249267578125e-05s
Believability | Calculation of trust value for MeSH titles took 7.152557373046875e-06s
INFO | --- Analysis for mesh_titles took 2.832509756088257s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.291534423828125e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2691078186035156s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.170967102050781e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 5.9604644775390625e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.8996429443359375s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.458427429199219e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.25983166694641113s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.123283386230469e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 6.198883056640625e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.8234901428222656s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 4.3392181396484375e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.28351616859436035s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.343292236328125e-05s
Believability | Calculation of trust value for MetaShare metadata model took 7.867813110351562e-06s
INFO | --- Analysis for metashare took 2.5108413696289062s
Availability | SPARQL endpoint availability check for MExiCo took 4.315376281738281e-05s
Availability | VoID file availability check for MExiCo took 0.0006988048553466797s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2589683532714844s
Reputation | Calculation of the PageRank for MExiCo took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.8160552978515625e-05s
Believability | Calculation of trust value for MExiCo took 6.4373016357421875e-06s
INFO | --- Analysis for mexico took 22.615628242492676s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.8059730529785156s
Availability | VoID file availability check for Coronavirus dataset took 0.0002727508544921875s
Extra | Recovery of all triples for Coronavirus dataset took 10.598037958145142s
Performance | Total latancy measurement for Coronavirus dataset took 2.4570446014404297s
Amount of data | Number of triples check for Coronavirus dataset took 1.1461408138275146s
Interoperability | New terms check for Coronavirus dataset took 2.483222723007202s
Versatility | Languages check for Coronavirus dataset took 60.52509117126465s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.638252019882202s
Interpretability | RDF structures check for Coronavirus dataset took 0.5254578590393066s
Versatility | Serialization formats check for Coronavirus dataset took 0.5466814041137695s
Availability | RDF dump link check for Coronavirus dataset took 0.5033495426177979s
License | MR license check for Coronavirus dataset took 0.5399425029754639s
License | HR license check for Coronavirus dataset took 41.05559778213501s
Amount of data | Number of property check for Coronavirus dataset took 0.5395159721374512s
Understandability | Number of label check for Coronavirus dataset took 1.3880255222320557s
Understandability | URI regex check for Coronavirus dataset took 0.9991676807403564s
Understandability | Vocabs check for Coronavirus dataset took 0.49790501594543457s
Verifiability | Authors check for Coronavirus dataset took 0.5223627090454102s
Verifiability | Publishers check for Coronavirus dataset took 0.489199161529541s
Performance | Throughput check for Coronavirus dataset took 14.376301765441895s
Amount of data | Check the number of entities for Coronavirus dataset took 7.009506225585938e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5004844665527344s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5204012393951416s
Interlinking | skos check for Coronavirus dataset took 0.5357911586761475s
Interlinking | skos check for Coronavirus dataset took 0.49259209632873535s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.497666597366333s
Currency | Creation date check for Coronavirus dataset took 1.0153121948242188s
Currency | Modification date check for Coronavirus dataset took 1.0139424800872803s
Rep.Conc. | URIs length for Coronavirus dataset took 8.948604106903076s
Interoperability | New vocabularies check for Coronavirus dataset took 3.5762786865234375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5097873210906982s
Accuracy | Check Functional Property for Coronavirus dataset took 0.7752561569213867s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.7443504333496094s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.400388717651367s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.027997970581054688s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.0289614200592041s
Consistency | Disjoint class check for Coronavirus dataset took 1.0700452327728271s
Consistency | Check Misplaced properties for Coronavirus dataset took 8.104069232940674s
Consistency | Misplaced classes for Coronavirus dataset took 0.624567985534668s
Consistency | Check Ontology hijacking for Coronavirus dataset took 3.958376884460449s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.145509958267212s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.587296962738037s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.03187274932861328s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5281805992126465s
Security | Sign check for Coronavirus dataset took 0.5315432548522949s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3093.972208738327s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.5396454334259033s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 6.29425048828125e-05s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for Coronavirus dataset took 1.1920928955078125e-05s
INFO | --- Analysis for micro-coronavirus took 3334.1283552646637s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.20159912109375e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.2732505798339844s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.019992589950561523s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.000102996826171875s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 5.854234218597412s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.410743713378906e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.26788783073425293s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010848045349121094s
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.774302959442139s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.09250950813293457s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.2707664966583252s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.863739013671875e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.3909759521484375e-06s
INFO | --- Analysis for mlsa took 3.800400972366333s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 5.7697296142578125e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.24933910369873047s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.9325485229492188e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 6.4373016357421875e-06s
INFO | --- Analysis for model took 33.42245030403137s
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.4345855712890625e-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.0006413459777832031s
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.7149238586425781s
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.020281314849853516s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007271766662597656s
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.337860107421875e-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 6.9141387939453125e-06s
INFO | --- Analysis for model1 took 18.754055738449097s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.887580871582031e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.2673332691192627s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.170967102050781e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 6.9141387939453125e-06s
INFO | --- Analysis for mond took 2.892061471939087s
Availability | SPARQL endpoint availability check for MONDIS took 4.1484832763671875e-05s
Availability | VoID file availability check for MONDIS took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for MONDIS took 0.25905489921569824s
Reputation | Calculation of the PageRank for MONDIS took 0.020174026489257812s
Interlinking | Calculation of Degree of Connection for MONDIS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MONDIS took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.8371810913085938e-05s
Believability | Calculation of trust value for MONDIS took 6.67572021484375e-06s
INFO | --- Analysis for mondis took 3.3339874744415283s
Availability | SPARQL endpoint availability check for Monumentos took 4.172325134277344e-05s
Availability | VoID file availability check for Monumentos took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Monumentos took 0.2655770778656006s
Reputation | Calculation of the PageRank for Monumentos took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for Monumentos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Monumentos took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.8848648071289062e-05s
Believability | Calculation of trust value for Monumentos took 6.4373016357421875e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.8203234672546387s
Availability | SPARQL endpoint availability check for MORElab took 0.9798176288604736s
Availability | VoID file availability check for MORElab took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for MORElab took 0.27132344245910645s
Reputation | Calculation of the PageRank for MORElab took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for MORElab took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MORElab took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for MORElab took 9.298324584960938e-05s
Believability | Calculation of trust value for MORElab took 6.9141387939453125e-06s
INFO | --- Analysis for morelab took 4.55583643913269s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 1.9966011047363281s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2596755027770996s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020198822021484375s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.58306884765625e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 8.106231689453125e-06s
INFO | --- Analysis for msc took 5.866546869277954s
Availability | SPARQL endpoint availability check for Multext-East took 4.363059997558594e-05s
Availability | VoID file availability check for Multext-East took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2732577323913574s
Reputation | Calculation of the PageRank for Multext-East took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for Multext-East took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.409385681152344e-05s
Believability | Calculation of trust value for Multext-East took 9.775161743164062e-06s
INFO | --- Analysis for multext-east took 2.2528603076934814s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.1961669921875e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.25317883491516113s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.02026224136352539s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 2.9802322387695312e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 6.9141387939453125e-06s
INFO | --- Analysis for multilingualeulaw took 2.7649948596954346s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.315376281738281e-05s
Availability | VoID file availability check for Multimedia Lab took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.259474515914917s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.600120544433594e-05s
Believability | Calculation of trust value for Multimedia Lab took 7.62939453125e-06s
INFO | --- Analysis for multimedia-lab took 2.368265390396118s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.1484832763671875e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.24402856826782227s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.0994415283203125e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 1.0013580322265625e-05s
INFO | --- Analysis for munich-offener-haushalt took 2.9095795154571533s
Availability | SPARQL endpoint availability check for Muninn World War I took 76.29642605781555s
Availability | VoID file availability check for Muninn World War I took 0.0005846023559570312s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2618978023529053s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.7738037109375e-05s
Believability | Calculation of trust value for Muninn World War I took 7.152557373046875e-06s
INFO | --- Analysis for muninn-world-war-i took 90.45228886604309s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.2438507080078125e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2924320697784424s
Reputation | Calculation of the PageRank for Musei Italiani took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.170967102050781e-05s
Believability | Calculation of trust value for Musei Italiani took 6.9141387939453125e-06s
INFO | --- Analysis for musei-italiani took 4.390488624572754s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.553794860839844e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2720909118652344s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0001087188720703125s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for museosespania-gnoss took 46.36867594718933s
Availability | SPARQL endpoint availability check for Italian Museums took 3.4394185543060303s
Availability | VoID file availability check for Italian Museums took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.27460598945617676s
Reputation | Calculation of the PageRank for Italian Museums took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 8.249282836914062e-05s
Believability | Calculation of trust value for Italian Museums took 6.9141387939453125e-06s
INFO | --- Analysis for museums-in-italy took 5.791044235229492s
Availability | SPARQL endpoint availability check for MusicBrainz took 5.0067901611328125e-05s
Availability | VoID file availability check for MusicBrainz took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.256852388381958s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.1948089599609375e-05s
Believability | Calculation of trust value for MusicBrainz took 8.106231689453125e-06s
INFO | --- Analysis for musicbrainz_ took 2.844723701477051s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.267692565917969e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.2379322052001953s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 3.075599670410156e-05s
Believability | Calculation of trust value for MusicNet Codex took 6.67572021484375e-06s
INFO | --- Analysis for musicnet_codex took 2.765993595123291s
Availability | SPARQL endpoint availability check for Muziekweb took 0.6683921813964844s
Availability | VoID file availability check for Muziekweb took 0.0006060600280761719s
Extra | Recovery of all triples for Muziekweb took 1.9988853931427002s
Performance | Total latancy measurement for Muziekweb took 1.4293413162231445s
Amount of data | Number of triples check for Muziekweb took 0.39610862731933594s
Interoperability | New terms check for Muziekweb took 1.6015090942382812s
Versatility | Languages check for Muziekweb took 58.3131422996521s
Interpretability | Number of blank nodes check for Muziekweb took 0.4829847812652588s
Interpretability | RDF structures check for Muziekweb took 0.7303657531738281s
Versatility | Serialization formats check for Muziekweb took 0.3151724338531494s
Availability | RDF dump link check for Muziekweb took 0.30786657333374023s
License | MR license check for Muziekweb took 0.3537921905517578s
License | HR license check for Muziekweb took 13.630881547927856s
Amount of data | Number of property check for Muziekweb took 0.28359055519104004s
Understandability | Number of label check for Muziekweb took 0.34297871589660645s
Understandability | URI regex check for Muziekweb took 0.6081790924072266s
Understandability | Vocabs check for Muziekweb took 0.4608473777770996s
Verifiability | Authors check for Muziekweb took 0.43073558807373047s
Verifiability | Publishers check for Muziekweb took 0.31062841415405273s
Performance | Throughput check for Muziekweb took 11.95710301399231s
Amount of data | Check the number of entities for Muziekweb took 7.557868957519531e-05s
Verifiability | Contribs. check for Muziekweb took 0.34805846214294434s
Interlinking | sameAs chians check for Muziekweb took 0.3013122081756592s
Interlinking | skos check for Muziekweb took 0.3110501766204834s
Interlinking | skos check for Muziekweb took 0.25162196159362793s
Timeliness | dataset update frequency check for Muziekweb took 0.296832799911499s
Currency | Creation date check for Muziekweb took 0.6032121181488037s
Currency | Modification date check for Muziekweb took 0.7035439014434814s
Rep.Conc. | URIs length for Muziekweb took 2.733647108078003s
Interoperability | New vocabularies check for Muziekweb took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.48042917251586914s
Accuracy | Check Functional Property for Muziekweb took 0.35430312156677246s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.3149600028991699s
Accuracy | Check Empty annotation labels for Muziekweb took 1.4323999881744385s
Accuracy | Check White space in annotation for Muziekweb took 0.034183502197265625s
Accuracy | Check Datatype consistency for Muziekweb took 0.028646230697631836s
Consistency | Disjoint class check for Muziekweb took 0.3376810550689697s
Consistency | Check Misplaced properties for Muziekweb took 1.2059874534606934s
Consistency | Check Ontology hijacking for Muziekweb took 1.9418351650238037s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.1432623863220215s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.4117114543914795s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03330373764038086s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3472414016723633s
Security | Sign check for Muziekweb took 0.3568737506866455s
Availability | Check URIs Dereferenciability for Muziekweb took 2018.2581751346588s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.4702134132385254s
Reputation | Calculation of the PageRank for Muziekweb took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for Muziekweb took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.1920928955078125e-06s
Believability | Calculation of trust value for Muziekweb took 8.344650268554688e-06s
INFO | --- Analysis for muziekweb took 2153.199926376343s
Availability | SPARQL endpoint availability check for myExperiment took 0.24730372428894043s
Availability | VoID file availability check for myExperiment took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for myExperiment took 0.6937515735626221s
Reputation | Calculation of the PageRank for myExperiment took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010085105895996094s
Believability | Calculation of trust value for myExperiment took 7.3909759521484375e-06s
INFO | --- Analysis for my-experiment took 5.187625885009766s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.075408935546875s
Availability | VoID file availability check for My Family Lineage took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.25804591178894043s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 9.083747863769531e-05s
Believability | Calculation of trust value for My Family Lineage took 6.9141387939453125e-06s
INFO | --- Analysis for my-family-lineage took 4.046124458312988s
Availability | SPARQL endpoint availability check for My ontology test took 0.6721088886260986s
Availability | VoID file availability check for My ontology test took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for My ontology test took 0.6925382614135742s
Reputation | Calculation of the PageRank for My ontology test took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.170967102050781e-05s
Believability | Calculation of trust value for My ontology test took 6.67572021484375e-06s
INFO | --- Analysis for myontologytest took 4.193503379821777s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 5.650520324707031e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.27576351165771484s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020875215530395508s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010657310485839844s
Believability | Calculation of trust value for myopenlink dataspaces took 6.198883056640625e-06s
INFO | --- Analysis for myopenlink-dataspaces took 2.724508762359619s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.14820122718811s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.24619412422180176s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020679712295532227s
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.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.724761962890625e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for n-lex-as-linked-data took 10.68227481842041s
Availability | SPARQL endpoint availability check for NAICS 2007 took 26.513470888137817s
Availability | VoID file availability check for NAICS 2007 took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.28034305572509766s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 4.029273986816406e-05s
Believability | Calculation of trust value for NAICS 2007 took 9.5367431640625e-06s
INFO | --- Analysis for naics-2007 took 127.19645810127258s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.45865035057068s
Availability | VoID file availability check for NAICS 2012 took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.258861780166626s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.02091193199157715s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0009927749633789062s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 7.104873657226562e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.245208740234375e-06s
INFO | --- Analysis for naics-2012 took 124.84290099143982s
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.0002598762512207031s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.26867175102233887s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 4.8160552978515625e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for nalt took 3.738664150238037s
Availability | SPARQL endpoint availability check for Usernames  took 4.506111145019531e-05s
Availability | VoID file availability check for Usernames  took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Usernames  took 0.24420809745788574s
Reputation | Calculation of the PageRank for Usernames  took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.0994415283203125e-05s
Believability | Calculation of trust value for Usernames  took 8.106231689453125e-06s
INFO | --- Analysis for Names took 2.915071725845337s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 2.005664110183716s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.00034546852111816406s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.0994513034820557s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.9897034168243408s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 12.673604726791382s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 22.06369924545288s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.4114358425140381s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 13.60436224937439s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.3791475296020508s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.3921365737915039s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.40822649002075195s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.3750114440917969s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.3903520107269287s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.76518774032593s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9908528327941895s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 5.751160383224487s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.7547917366027832s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.41898369789123535s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.36797595024108887s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.3714430332183838s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.773926258087158s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 8.463859558105469e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.40475988388061523s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5333380699157715s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.561305284500122s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.3463106155395508s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.41486692428588867s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.165548324584961s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.8241550922393799s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.0195369720458984s
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.4240121841430664s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.40030980110168457s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.3740725517272949s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.3870813846588135s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0007445812225341797s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0010063648223876953s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.40288734436035156s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.8001143932342529s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.4019653797149658s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.6226141452789307s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.1931681632995605s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.5508482456207275s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006427764892578125s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.4048004150390625s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 4.233181953430176s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.24810433387756348s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.626678466796875e-05s
Interoperability | Check the re-using of existing vocabs for Web NDL Authorities - National Diet Library of Japan took 1.6689300537109375e-06s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 4.76837158203125e-06s
INFO | --- Analysis for national-diet-library-authorities took 236.09885787963867s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.38617849349975586s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0006272792816162109s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.4285483360290527s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.994230031967163s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 11.898537635803223s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.8968400955200195s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 17.3860445022583s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3669393062591553s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.3901522159576416s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.4239218235015869s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.35195159912109375s
License | MR license check for National Diet Library of Japan subject headings took 0.3884236812591553s
License | HR license check for National Diet Library of Japan subject headings took 91.72033381462097s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.9129562377929688s
Understandability | Number of label check for National Diet Library of Japan subject headings took 5.52424430847168s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7081553936004639s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.41639161109924316s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3707156181335449s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.4310727119445801s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.723129034042358s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 9.417533874511719e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.3900165557861328s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.48630356788635254s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.5432865619659424s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.5339758396148682s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.4052155017852783s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.1593878269195557s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.8386092185974121s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 1.0450844764709473s
Interoperability | New vocabularies check for National Diet Library of Japan subject headings took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Diet Library of Japan subject headings took 0.41542696952819824s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.4016900062561035s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.3486320972442627s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.4171583652496338s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007946491241455078s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010504722595214844s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.44569873809814453s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.8401072025299072s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.37175726890563965s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.5808470249176025s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.173269510269165s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.5610384941101074s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006062984466552734s
Security | Sign check for National Diet Library of Japan subject headings took 0.3463912010192871s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 4.04620099067688s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.8204071521759033s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.0067901611328125e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 8.106231689453125e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 305.7455213069916s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.8900530338287354s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0005631446838378906s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.7013399600982666s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.124641418457031e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 3.528594970703125e-05s
INFO | --- Analysis for national-library-of-greece-authority-records took 5.5828633308410645s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.38690185546875e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.26598644256591797s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007719993591308594s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.866455078125e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.152557373046875e-06s
INFO | --- Analysis for Naturopathy took 3.389890670776367s
Availability | SPARQL endpoint availability check for Naturopathy took 4.220008850097656e-05s
Availability | VoID file availability check for Naturopathy took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.25138354301452637s
Reputation | Calculation of the PageRank for Naturopathy took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Naturopathy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.86102294921875e-05s
Believability | Calculation of trust value for Naturopathy took 6.4373016357421875e-06s
INFO | --- Analysis for naturopathy2 took 2.859780788421631s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 5.4836273193359375e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2514224052429199s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for NCI Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for nci-thesaurus took 2.8385329246520996s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.379608631134033s
Availability | VoID file availability check for COVID-19 Data took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.27300143241882324s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.123283386230469e-05s
Believability | Calculation of trust value for COVID-19 Data took 6.9141387939453125e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.689960479736328s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.4008092880249023s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.2472059726715088s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.021060705184936523s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2159347534179688e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 6.67572021484375e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.195582866668701s
Availability | SPARQL endpoint availability check for NDF-RT took 4.220008850097656e-05s
Availability | VoID file availability check for NDF-RT took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.26857852935791016s
Reputation | Calculation of the PageRank for NDF-RT took 0.020138978958129883s
Interlinking | Calculation of Degree of Connection for NDF-RT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 2.765655517578125e-05s
Believability | Calculation of trust value for NDF-RT took 7.152557373046875e-06s
INFO | --- Analysis for ndf-rt took 2.94343900680542s
Availability | SPARQL endpoint availability check for Near took 4.2438507080078125e-05s
Availability | VoID file availability check for Near took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for Near took 0.28062891960144043s
Reputation | Calculation of the PageRank for Near took 0.0201108455657959s
Interlinking | Calculation of Degree of Connection for Near took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Near took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Near took 9.036064147949219e-05s
Believability | Calculation of trust value for Near took 7.867813110351562e-06s
INFO | --- Analysis for near took 9.46252727508545s
Availability | SPARQL endpoint availability check for Neel took 4.124641418457031e-05s
Availability | VoID file availability check for Neel took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Neel took 0.27195191383361816s
Reputation | Calculation of the PageRank for Neel took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for Neel took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neel took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Neel took 2.86102294921875e-05s
Believability | Calculation of trust value for Neel took 6.4373016357421875e-06s
INFO | --- Analysis for neel took 2.9371390342712402s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.172325134277344e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.26479363441467285s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.600120544433594e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 6.67572021484375e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.9363644123077393s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.267692565917969e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.26409912109375s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.0517578125e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 5.7220458984375e-06s
INFO | --- Analysis for neurolex-wiki took 2.415351152420044s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 5.3882598876953125e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.2551274299621582s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.02030014991760254s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.172325134277344e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 6.198883056640625e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.806169033050537s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.38690185546875e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0006096363067626953s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.26733827590942383s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.747245788574219e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 8.106231689453125e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 3.4110591411590576s
Availability | SPARQL endpoint availability check for Newsweek took 4.172325134277344e-05s
Availability | VoID file availability check for Newsweek took 0.0003943443298339844s
Completeness | Calculation of interlinking completeness for Newsweek took 0.2638671398162842s
Reputation | Calculation of the PageRank for Newsweek took 0.020212650299072266s
Interlinking | Calculation of Degree of Connection for Newsweek took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.0040740966796875e-05s
Believability | Calculation of trust value for Newsweek took 6.9141387939453125e-06s
INFO | --- Analysis for newsweek took 2.929825782775879s
Availability | SPARQL endpoint availability check for neXtProt took 3.2206573486328125s
Availability | VoID file availability check for neXtProt took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for neXtProt took 0.268024206161499s
Reputation | Calculation of the PageRank for neXtProt took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for neXtProt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for neXtProt took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.647804260253906e-05s
Believability | Calculation of trust value for neXtProt took 7.62939453125e-06s
INFO | --- Analysis for nextprot took 6.5360448360443115s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.482269287109375e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0005316734313964844s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2537987232208252s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.02162957191467285s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010657310485839844s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 6.198883056640625e-06s
INFO | --- Analysis for nextweb-gnoss took 4.844395875930786s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.410743713378906e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.27622556686401367s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.987022399902344e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 4.76837158203125e-06s
INFO | --- Analysis for nhs-jargon took 2.7659738063812256s
Availability | SPARQL endpoint availability check for NIT Patna took 4.267692565917969e-05s
Availability | VoID file availability check for NIT Patna took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.26373291015625s
Reputation | Calculation of the PageRank for NIT Patna took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for NIT Patna took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.794929504394531e-05s
Believability | Calculation of trust value for NIT Patna took 5.9604644775390625e-06s
INFO | --- Analysis for NITP took 3.2154700756073s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 4.220008850097656e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.000244140625s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.23773455619812012s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.504753112792969e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 1.3113021850585938e-05s
INFO | --- Analysis for nlm_2007_mesh took 2.8233065605163574s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.982948303222656e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.24091053009033203s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 6.67572021484375e-06s
INFO | --- Analysis for nlr-dataset-mod took 4.058943271636963s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5039548873901367s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.2817556858062744s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for NLW took 3.964451789855957s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.105823516845703s
Availability | VoID file availability check for Nobel Prizes took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.26135778427124023s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.751319885253906e-05s
Believability | Calculation of trust value for Nobel Prizes took 5.7220458984375e-06s
INFO | --- Analysis for nobelprizes took 7.813250541687012s
Availability | SPARQL endpoint availability check for NoiPA took 0.34423017501831055s
Availability | VoID file availability check for NoiPA took 0.00024318695068359375s
Extra | Recovery of all triples for NoiPA took 76.68606328964233s
Performance | Total latancy measurement for NoiPA took 0.6070380210876465s
Amount of data | Number of triples check for NoiPA took 3.5514748096466064s
Interoperability | New terms check for NoiPA took 2.9461722373962402s
Versatility | Languages check for NoiPA took 60.12497401237488s
Interpretability | Number of blank nodes check for NoiPA took 0.19297337532043457s
Interpretability | RDF structures check for NoiPA took 0.24108362197875977s
Versatility | Serialization formats check for NoiPA took 0.14914417266845703s
Availability | RDF dump link check for NoiPA took 0.20953822135925293s
License | MR license check for NoiPA took 0.2340528964996338s
License | HR license check for NoiPA took 60.17696452140808s
Amount of data | Number of property check for NoiPA took 0.15072226524353027s
Understandability | Number of label check for NoiPA took 0.5710339546203613s
Understandability | URI regex check for NoiPA took 0.366560697555542s
Understandability | Vocabs check for NoiPA took 0.10851454734802246s
Verifiability | Authors check for NoiPA took 0.11786270141601562s
Verifiability | Publishers check for NoiPA took 0.08846712112426758s
Performance | Throughput check for NoiPA took 10.545176982879639s
Amount of data | Check the number of entities for NoiPA took 0.00011491775512695312s
Verifiability | Contribs. check for NoiPA took 0.11911153793334961s
Interlinking | sameAs chians check for NoiPA took 0.1531541347503662s
Interlinking | skos check for NoiPA took 0.5977072715759277s
Interlinking | skos check for NoiPA took 0.08481788635253906s
Timeliness | dataset update frequency check for NoiPA took 0.1259300708770752s
Currency | Creation date check for NoiPA took 0.25684309005737305s
Currency | Modification date check for NoiPA took 0.17398476600646973s
Rep.Conc. | URIs length for NoiPA took 50.92661952972412s
Interoperability | New vocabularies check for NoiPA took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.10971474647521973s
Accuracy | Check Functional Property for NoiPA took 0.16846537590026855s
Accuracy | Check Inverse Functional Property for NoiPA took 0.17880773544311523s
Accuracy | Check Empty annotation labels for NoiPA took 25.233476638793945s
Accuracy | Check White space in annotation for NoiPA took 2.257157802581787s
Accuracy | Check Datatype consistency for NoiPA took 2.00907039642334s
Consistency | Disjoint class check for NoiPA took 0.13398432731628418s
Consistency | Check Misplaced properties for NoiPA took 19.274463653564453s
Consistency | Misplaced classes for NoiPA took 6.194401502609253s
Consistency | Check Ontology hijacking for NoiPA took 24.037248611450195s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.5131373405456543s
Consistency | Check Invalid usage of undefined properties for NoiPA took 20.531556606292725s
Conciseness | Check Extensional conciseness for NoiPA took 2.163985252380371s
Conciseness | Check Intensional conciseness for NoiPA took 0.1490476131439209s
Security | Sign check for NoiPA took 0.15457916259765625s
Availability | Check URIs Dereferenciability for NoiPA took 12.417182683944702s
Completeness | Calculation of interlinking completeness for NoiPA took 0.9391429424285889s
Reputation | Calculation of the PageRank for NoiPA took 0.021265268325805664s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.361701965332031e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.9073486328125e-06s
Believability | Calculation of trust value for NoiPA took 1.71661376953125e-05s
INFO | --- Analysis for NoiPA took 571.7165830135345s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.2257606983184814s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.26355957984924316s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.393692016601562e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 8.344650268554688e-06s
INFO | --- Analysis for nom took 25.208489179611206s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 25.333678245544434s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008382797241210938s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2650432586669922s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.630752563476562e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.0067901611328125e-06s
INFO | --- Analysis for nomenclator-asturias took 138.57154726982117s
Availability | SPARQL endpoint availability check for nomisma took 4.220008850097656e-05s
Availability | VoID file availability check for nomisma took 0.0003104209899902344s
Completeness | Calculation of interlinking completeness for nomisma took 0.26354002952575684s
Reputation | Calculation of the PageRank for nomisma took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for nomisma took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for nomisma took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.1948089599609375e-05s
Believability | Calculation of trust value for nomisma took 6.67572021484375e-06s
INFO | --- Analysis for nomisma took 3.806579351425171s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.5117712020874023s
Availability | VoID file availability check for Nomisma.org  took 0.0005927085876464844s
Extra | Recovery of all triples for Nomisma.org  took 493.9155580997467s
Performance | Total latancy measurement for Nomisma.org  took 2.0721120834350586s
Amount of data | Number of triples check for Nomisma.org  took 44.15898323059082s
Interoperability | New terms check for Nomisma.org  took 7.228221893310547s
Versatility | Languages check for Nomisma.org  took 105.76928281784058s
Interpretability | Number of blank nodes check for Nomisma.org  took 31.985572576522827s
Security | Check HTTPS for Nomisma.org  took 1.4357967376708984s
Interpretability | RDF structures check for Nomisma.org  took 0.4527561664581299s
Versatility | Serialization formats check for Nomisma.org  took 0.6370055675506592s
Availability | RDF dump link check for Nomisma.org  took 1366.9052503108978s
License | MR license check for Nomisma.org  took 0.6456191539764404s
License | HR license check for Nomisma.org  took 60.584080934524536s
Amount of data | Number of property check for Nomisma.org  took 0.5088891983032227s
Understandability | Number of label check for Nomisma.org  took 11.165557146072388s
Understandability | URI regex check for Nomisma.org  took 2.058350086212158s
Understandability | Vocabs check for Nomisma.org  took 0.40621399879455566s
Verifiability | Authors check for Nomisma.org  took 0.5161657333374023s
Verifiability | Publishers check for Nomisma.org  took 0.8686020374298096s
Performance | Throughput check for Nomisma.org  took 14.893766403198242s
Amount of data | Check the number of entities for Nomisma.org  took 7.939338684082031e-05s
Verifiability | Contribs. check for Nomisma.org  took 1.979320764541626s
Interlinking | sameAs chians check for Nomisma.org  took 0.17677521705627441s
Interlinking | skos check for Nomisma.org  took 0.14457178115844727s
Interlinking | skos check for Nomisma.org  took 14.8433256149292s
Timeliness | dataset update frequency check for Nomisma.org  took 0.486767053604126s
Currency | Creation date check for Nomisma.org  took 0.6611275672912598s
Currency | Modification date check for Nomisma.org  took 0.6188473701477051s
Rep.Conc. | URIs length for Nomisma.org  took 0.6833381652832031s
Interoperability | New vocabularies check for Nomisma.org  took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.31556272506713867s
Consistency | Disjoint class check for Nomisma.org  took 0.33458614349365234s
Consistency | Check Ontology hijacking for Nomisma.org  took 0.2995116710662842s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 1.5423874855041504s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.00012874603271484375s
Security | Sign check for Nomisma.org  took 0.3128788471221924s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.5947942733764648s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.1920928955078125e-06s
Believability | Calculation of trust value for Nomisma.org  took 8.106231689453125e-06s
INFO | --- Analysis for nomisma_org took 2521.9795689582825s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.9072613716125488s
Availability | VoID file availability check for Curriculum Vitae took 0.0002677440643310547s
Extra | Recovery of all triples for Curriculum Vitae took 3.1513562202453613s
Performance | Total latancy measurement for Curriculum Vitae took 1.2018101215362549s
Amount of data | Number of triples check for Curriculum Vitae took 0.29184746742248535s
Interoperability | New terms check for Curriculum Vitae took 1.424379825592041s
Versatility | Languages check for Curriculum Vitae took 0.253115177154541s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.35457563400268555s
Interpretability | RDF structures check for Curriculum Vitae took 0.12676429748535156s
Versatility | Serialization formats check for Curriculum Vitae took 0.45807504653930664s
Availability | RDF dump link check for Curriculum Vitae took 0.10877370834350586s
License | MR license check for Curriculum Vitae took 0.12008333206176758s
License | HR license check for Curriculum Vitae took 0.2585270404815674s
Amount of data | Number of property check for Curriculum Vitae took 0.23359966278076172s
Understandability | Number of label check for Curriculum Vitae took 0.24211788177490234s
Understandability | URI regex check for Curriculum Vitae took 0.2533402442932129s
Understandability | Vocabs check for Curriculum Vitae took 0.13157010078430176s
Verifiability | Authors check for Curriculum Vitae took 0.2556302547454834s
Verifiability | Publishers check for Curriculum Vitae took 0.2280740737915039s
Performance | Throughput check for Curriculum Vitae took 10.807615756988525s
Amount of data | Check the number of entities for Curriculum Vitae took 7.390975952148438e-05s
Verifiability | Contribs. check for Curriculum Vitae took 0.13625741004943848s
Interlinking | sameAs chians check for Curriculum Vitae took 0.22818493843078613s
Interlinking | skos check for Curriculum Vitae took 0.22803592681884766s
Interlinking | skos check for Curriculum Vitae took 0.12447977066040039s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.21142292022705078s
Currency | Creation date check for Curriculum Vitae took 0.34709882736206055s
Currency | Modification date check for Curriculum Vitae took 0.2616872787475586s
Rep.Conc. | URIs length for Curriculum Vitae took 0.7736294269561768s
Interoperability | New vocabularies check for Curriculum Vitae took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.1273643970489502s
Accuracy | Check Functional Property for Curriculum Vitae took 0.11791801452636719s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.11956596374511719s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.23385310173034668s
Accuracy | Check White space in annotation for Curriculum Vitae took 9.179115295410156e-05s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0034236907958984375s
Consistency | Disjoint class check for Curriculum Vitae took 0.22086310386657715s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.38455867767333984s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.305539846420288s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.1874356269836426s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 1.4203112125396729s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0013217926025390625s
Security | Sign check for Curriculum Vitae took 0.24450325965881348s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 21.71598243713379s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.6970357894897461s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020801782608032227s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 3.218650817871094e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 1.1920928955078125e-06s
Believability | Calculation of trust value for Curriculum Vitae took 7.152557373046875e-06s
INFO | --- Analysis for Nordine_Bittich took 67.97774124145508s
Availability | SPARQL endpoint availability check for NorPark took 0.19043636322021484s
Availability | VoID file availability check for NorPark took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for NorPark took 0.24086833000183105s
Reputation | Calculation of the PageRank for NorPark took 0.020714998245239258s
Interlinking | Calculation of Degree of Connection for NorPark took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for NorPark took 5.1975250244140625e-05s
Believability | Calculation of trust value for NorPark took 6.9141387939453125e-06s
INFO | --- Analysis for norpark took 4.079260587692261s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.02433323860168457s
Availability | VoID file availability check for Parking Dataset took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.25531840324401855s
Reputation | Calculation of the PageRank for Parking Dataset took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.4345855712890625e-05s
Believability | Calculation of trust value for Parking Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for norpark2 took 2.834010601043701s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.6057581901550293s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.000247955322265625s
Extra | Recovery of all triples for Norway fishery stocks dataset took 115.48460793495178s
Performance | Total latancy measurement for Norway fishery stocks dataset took 1.041154146194458s
Amount of data | Number of triples check for Norway fishery stocks dataset took 8.207874059677124s
Interoperability | New terms check for Norway fishery stocks dataset took 13.492022037506104s
Versatility | Languages check for Norway fishery stocks dataset took 300.2020766735077s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 3.2283949851989746s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.24872684478759766s
Versatility | Serialization formats check for Norway fishery stocks dataset took 10.240680694580078s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.3041250705718994s
License | MR license check for Norway fishery stocks dataset took 0.6629641056060791s
License | HR license check for Norway fishery stocks dataset took 300.2035057544708s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.32183170318603516s
Understandability | Number of label check for Norway fishery stocks dataset took 2.339806079864502s
Understandability | URI regex check for Norway fishery stocks dataset took 0.599158763885498s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.2717876434326172s
Verifiability | Authors check for Norway fishery stocks dataset took 0.1984248161315918s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.248945951461792s
Performance | Throughput check for Norway fishery stocks dataset took 11.488927125930786s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 0.00011014938354492188s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.21190714836120605s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.2207317352294922s
Interlinking | skos check for Norway fishery stocks dataset took 0.529266357421875s
Interlinking | skos check for Norway fishery stocks dataset took 0.4259951114654541s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 5.599299192428589s
Currency | Creation date check for Norway fishery stocks dataset took 0.4870157241821289s
Currency | Modification date check for Norway fishery stocks dataset took 0.23049545288085938s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 151.2645275592804s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.2186429500579834s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.2767984867095947s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.27697157859802246s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 44.79015111923218s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.715747594833374s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.623159646987915s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.1999495029449463s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 83.70159649848938s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.676227331161499s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 36.42578911781311s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.3115038871765137s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 81.52996826171875s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7419254779815674s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.629310131072998s
Security | Sign check for Norway fishery stocks dataset took 0.5652780532836914s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.282517433166504s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 1.4829838275909424s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.100799560546875e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 8.106231689453125e-06s
INFO | --- Analysis for Norway_Fishery_ took 2269.6216955184937s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.3556208610534668s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0005757808685302734s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.27658915519714355s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.0067901611328125e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 8.58306884765625e-06s
INFO | --- Analysis for norwegian-geo-divisions took 7.331707715988159s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.3392181396484375e-05s
Availability | VoID file availability check for NorwegianSoE took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.6986167430877686s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0009496212005615234s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.838539123535156e-05s
Believability | Calculation of trust value for NorwegianSoE took 7.867813110351562e-06s
INFO | --- Analysis for norwegiansoe took 3.7625370025634766s
Availability | SPARQL endpoint availability check for NITP took 4.649162292480469e-05s
Availability | VoID file availability check for NITP took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for NITP took 0.26554107666015625s
Reputation | Calculation of the PageRank for NITP took 0.02101755142211914s
Interlinking | Calculation of Degree of Connection for NITP took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NITP took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for NITP took 6.985664367675781e-05s
Believability | Calculation of trust value for NITP took 6.9141387939453125e-06s
INFO | --- Analysis for notIdentifier took 3.935185432434082s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.38690185546875e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.2508509159088135s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.021005868911743164s
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.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.695487976074219e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 5.0067901611328125e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.7113964557647705s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.1961669921875e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.26633715629577637s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 3.170967102050781e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 6.67572021484375e-06s
INFO | --- Analysis for npg took 3.2437286376953125s
Availability | SPARQL endpoint availability check for NPM took 4.506111145019531e-05s
Availability | VoID file availability check for NPM took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for NPM took 0.26932597160339355s
Reputation | Calculation of the PageRank for NPM took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for NPM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for NPM took 3.552436828613281e-05s
Believability | Calculation of trust value for NPM took 7.867813110351562e-06s
INFO | --- Analysis for npm took 3.193495512008667s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.03240776062011719s
Availability | VoID file availability check for NTNU special collections took 0.0012745857238769531s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.26407384872436523s
Reputation | Calculation of the PageRank for NTNU special collections took 0.020867109298706055s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.888938903808594e-05s
Believability | Calculation of trust value for NTNU special collections took 8.58306884765625e-06s
INFO | --- Analysis for ntnusc took 4.959801912307739s
Availability | SPARQL endpoint availability check for links took 4.315376281738281e-05s
Availability | VoID file availability check for links took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for links took 0.2542388439178467s
Reputation | Calculation of the PageRank for links took 0.020641565322875977s
Interlinking | Calculation of Degree of Connection for links took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for links took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for links took 1.2874603271484375e-05s
Believability | Calculation of trust value for links took 5.9604644775390625e-06s
INFO | --- Analysis for nugmyanmar took 2.3403096199035645s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 5.555152893066406e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0005679130554199219s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.26589274406433105s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.989738464355469e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 4.76837158203125e-06s
INFO | --- Analysis for nuts-geovocab took 8.357714891433716s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.3958101272583008s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.26232242584228516s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.020093679428100586s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.033348083496094e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 7.62939453125e-06s
INFO | --- Analysis for nvd took 3.9624462127685547s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.7624163627624512s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.25792622566223145s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.153915405273438e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 7.3909759521484375e-06s
INFO | --- Analysis for nvs took 8.315350770950317s
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.0004494190216064453s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.25659871101379395s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.000186920166015625s
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.4250221252441406s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.100799560546875e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.26408886909484863s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.2901763916015625e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 7.152557373046875e-06s
INFO | --- Analysis for o-anc took 2.886596918106079s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.076957702636719e-05s
Availability | VoID file availability check for OANetzwerk took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.2459714412689209s
Reputation | Calculation of the PageRank for OANetzwerk took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 3.218650817871094e-05s
Believability | Calculation of trust value for OANetzwerk took 9.5367431640625e-06s
INFO | --- Analysis for oanetzwerk took 2.869957447052002s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 4.291534423828125e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2770867347717285s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.123283386230469e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 6.67572021484375e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.9719793796539307s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.4883120059967041s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006272792816162109s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.9482927322387695s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.6049871444702148s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.7901716232299805s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.749368190765381s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.287410497665405s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.6575076580047607s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.24161434173583984s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.38132715225219727s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.47035861015319824s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.29435086250305176s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.32313060760498047s
License | HR license check for Italian Chamber of Deputies - official dataset took 0.32799506187438965s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.2512702941894531s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.3481762409210205s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.663794994354248s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.3271481990814209s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.30599188804626465s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.27854228019714355s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 0.0001609325408935547s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.33794307708740234s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.31839847564697266s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.3359260559082031s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.33014917373657227s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 0.3400390148162842s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6803700923919678s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.641019344329834s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 0.6359245777130127s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.31514668464660645s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.029906749725341797s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.30985236167907715s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 0.23196673393249512s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 1.5230591297149658s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03046250343322754s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.31818199157714844s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 11.79456090927124s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3190419673919678s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00010251998901367188s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 7.152557373046875e-07s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 7.152557373046875e-06s
INFO | --- Analysis for ocd took 164.6454141139984s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.315376281738281e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2663760185241699s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.019908428192138672s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.600120544433594e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 1.2636184692382812e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.6248841285705566s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.3557794094085693s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.26917552947998047s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0008051395416259766s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 9.322166442871094e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-codices took 8.11076283454895s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2105967998504639s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.25698256492614746s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 6.4373016357421875e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 5.957834720611572s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.2548890113830566s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2583324909210205s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020116090774536133s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.2901763916015625e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-forams took 5.949045181274414s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.1711084842681885s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0003337860107421875s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.25789499282836914s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020239830017089844s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.147125244140625e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-janus took 7.170417308807373s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.126839399337769s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.27303314208984375s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020819425582885742s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.4809112548828125e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-janusamp took 16.064480543136597s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.488114833831787s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006227493286132812s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2726593017578125s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.4373016357421875e-06s
INFO | --- Analysis for oceandrilling-ldeo took 13.183514833450317s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.38690185546875e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0005764961242675781s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.28159523010253906s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 5.7697296142578125e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.1920928955078125e-05s
INFO | --- Analysis for oclc-fast took 7.985380172729492s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.1961669921875e-05s
Availability | VoID file availability check for Open Data Communities took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2686295509338379s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 2.7179718017578125e-05s
Believability | Calculation of trust value for Open Data Communities took 5.9604644775390625e-06s
INFO | --- Analysis for odc took 2.8515419960021973s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.291534423828125e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2709004878997803s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.02066493034362793s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007412433624267578s
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 4.5299530029296875e-06s
INFO | --- Analysis for odc-imd-environment-score took 3.3754732608795166s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.458427429199219e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2638547420501709s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020197153091430664s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 6.4373016357421875e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 2.7760584354400635s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.21781635284423828s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.26355552673339844s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.02019047737121582s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.4332275390625e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 9.059906005859375e-06s
INFO | --- Analysis for odc-lsoa took 3.4702060222625732s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.100799560546875e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.2639632225036621s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 6.67572021484375e-06s
INFO | --- Analysis for odc-population-2005 took 2.9392168521881104s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.124641418457031e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.25801682472229004s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 6.4373016357421875e-06s
INFO | --- Analysis for ods took 2.8363988399505615s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.39051365852355957s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.24948906898498535s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.393692016601562e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for oecd-linked-data took 2.758338689804077s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.1484832763671875e-05s
Availability | VoID file availability check for Offener Haushalt took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.25039243698120117s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.9325485229492188e-05s
Believability | Calculation of trust value for Offener Haushalt took 6.4373016357421875e-06s
INFO | --- Analysis for offener-haushalt took 2.857692241668701s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.205901861190796s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006566047668457031s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2599802017211914s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.0531158447265625e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 6.4373016357421875e-06s
INFO | --- Analysis for ogolod took 102.63563966751099s
Availability | SPARQL endpoint availability check for OLAC Metadata took 6.866455078125e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0007641315460205078s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.2744622230529785s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.886222839355469e-05s
Believability | Calculation of trust value for OLAC Metadata took 8.106231689453125e-06s
INFO | --- Analysis for olac took 22.5718674659729s
Availability | SPARQL endpoint availability check for OLiA took 4.363059997558594e-05s
Availability | VoID file availability check for OLiA took 0.0007746219635009766s
Completeness | Calculation of interlinking completeness for OLiA took 0.27030467987060547s
Reputation | Calculation of the PageRank for OLiA took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for OLiA took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00011992454528808594s
Believability | Calculation of trust value for OLiA took 7.867813110351562e-06s
INFO | --- Analysis for olia took 12.42515230178833s
Availability | SPARQL endpoint availability check for OLiA Discourse took 5.0067901611328125e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0007519721984863281s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.266585111618042s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.124641418457031e-05s
Believability | Calculation of trust value for OLiA Discourse took 7.152557373046875e-06s
INFO | --- Analysis for olia-discourse took 7.424614906311035s
Availability | SPARQL endpoint availability check for Open Land Use took 0.19209957122802734s
Availability | VoID file availability check for Open Land Use took 0.0006890296936035156s
Extra | Recovery of all triples for Open Land Use took 120.96238684654236s
Performance | Total latancy measurement for Open Land Use took 1.1459276676177979s
Amount of data | Number of triples check for Open Land Use took 7.756204605102539s
Interoperability | New terms check for Open Land Use took 13.905714511871338s
Versatility | Languages check for Open Land Use took 300.2263548374176s
Interpretability | Number of blank nodes check for Open Land Use took 3.209850311279297s
Interpretability | RDF structures check for Open Land Use took 0.25374627113342285s
Versatility | Serialization formats check for Open Land Use took 11.466132640838623s
Availability | RDF dump link check for Open Land Use took 0.2852482795715332s
License | MR license check for Open Land Use took 0.5941195487976074s
License | HR license check for Open Land Use took 300.2069272994995s
Amount of data | Number of property check for Open Land Use took 0.333528995513916s
Understandability | Number of label check for Open Land Use took 2.260768175125122s
Understandability | URI regex check for Open Land Use took 0.5664877891540527s
Understandability | Vocabs check for Open Land Use took 0.2634568214416504s
Verifiability | Authors check for Open Land Use took 0.20741915702819824s
Verifiability | Publishers check for Open Land Use took 0.2606351375579834s
Performance | Throughput check for Open Land Use took 11.604062557220459s
Amount of data | Check the number of entities for Open Land Use took 8.630752563476562e-05s
Verifiability | Contribs. check for Open Land Use took 0.19917607307434082s
Interlinking | sameAs chians check for Open Land Use took 0.1947307586669922s
Interlinking | skos check for Open Land Use took 0.44449496269226074s
Interlinking | skos check for Open Land Use took 0.4582793712615967s
Timeliness | dataset update frequency check for Open Land Use took 6.602287530899048s
Currency | Creation date check for Open Land Use took 0.5158376693725586s
Currency | Modification date check for Open Land Use took 0.24078607559204102s
Rep.Conc. | URIs length for Open Land Use took 154.48307085037231s
Interoperability | New vocabularies check for Open Land Use took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.1838991641998291s
Accuracy | Check Functional Property for Open Land Use took 0.24226927757263184s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.24510502815246582s
Accuracy | Check Empty annotation labels for Open Land Use took 43.89419484138489s
Accuracy | Check White space in annotation for Open Land Use took 2.7028703689575195s
Accuracy | Check Datatype consistency for Open Land Use took 2.6196632385253906s
Consistency | Disjoint class check for Open Land Use took 0.21013784408569336s
Consistency | Check Misplaced properties for Open Land Use took 87.0298228263855s
Consistency | Misplaced classes for Open Land Use took 8.491042375564575s
Consistency | Check Ontology hijacking for Open Land Use took 40.249520778656006s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.2357487678527832s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 87.39064884185791s
Conciseness | Check Extensional conciseness for Open Land Use took 2.700364828109741s
Conciseness | Check Intensional conciseness for Open Land Use took 0.604827880859375s
Security | Sign check for Open Land Use took 0.47999119758605957s
Availability | Check URIs Dereferenciability for Open Land Use took 9.58103609085083s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.9765136241912842s
Reputation | Calculation of the PageRank for Open Land Use took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Land Use took 7.3909759521484375e-06s
INFO | --- Analysis for OLU took 2284.676906108856s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.172325134277344e-05s
Availability | VoID file availability check for OmegaWiki took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.2447044849395752s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 2.9087066650390625e-05s
Believability | Calculation of trust value for OmegaWiki took 7.3909759521484375e-06s
INFO | --- Analysis for omegawiki took 4.367351055145264s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6737456321716309s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.27097082138061523s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.02015542984008789s
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.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-als took 4.3368730545043945s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2619028091430664s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0003535747528076172s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.27544546127319336s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-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.4668805599212646s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.23452091217041016s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.6956512928009033s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-bul took 3.4183101654052734s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2740781307220459s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00035262107849121094s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.250152587890625s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020433664321899414s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-cow took 2.929640054702759s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.25028085708618164s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004239082336425781s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2656896114349365s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-cwn took 2.9701313972473145s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.23977303504943848s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.25414514541625977s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020903587341308594s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.1961669921875e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-dan took 3.0126333236694336s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.23703527450561523s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2541682720184326s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
INFO | --- Analysis for omwn-ell took 2.9077022075653076s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.22391486167907715s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2642703056335449s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02130603790283203s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 4.410743713378906e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-eng took 2.9826693534851074s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.2496509552001953s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.26563048362731934s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.0205078125s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-fas took 3.0106558799743652s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.22435998916625977s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.24095892906188965s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.020585298538208008s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-fin took 2.884608507156372s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.22273778915405273s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2588620185852051s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
INFO | --- Analysis for omwn-fra took 2.9809763431549072s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.24346423149108887s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.26567697525024414s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 5.7220458984375e-06s
INFO | --- Analysis for omwn-heb took 2.9070382118225098s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.22876262664794922s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.25879573822021484s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 5.4836273193359375e-06s
INFO | --- Analysis for omwn-hrv took 2.967912435531616s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.23449015617370605s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.25532078742980957s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020179271697998047s
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.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-isl took 2.8886892795562744s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2200758457183838s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.27585530281066895s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.267692565917969e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 5.9604644775390625e-06s
INFO | --- Analysis for omwn-ita took 2.904848337173462s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.20723176002502441s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2598695755004883s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020220041275024414s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.933906555175781e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-iwn took 2.8649675846099854s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.22833538055419922s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.00043463706970214844s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2651515007019043s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-jpn took 2.9196853637695312s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.22580933570861816s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.00035834312438964844s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.24701547622680664s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-mcr took 2.954307794570923s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.22440385818481445s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.24845290184020996s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-msa took 2.8771166801452637s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.2337789535522461s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.22744274139404297s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-nld took 2.877915620803833s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.21044373512268066s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2574143409729004s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0204012393951416s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0009350776672363281s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.410743713378906e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-nor took 2.8258931636810303s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.22626090049743652s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2535257339477539s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 4.220008850097656e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-pol took 2.8029215335845947s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.24250483512878418s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2579154968261719s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.020231246948242188s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-por took 2.940655469894409s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.22667813301086426s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2500925064086914s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-ron took 2.902787446975708s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.23152565956115723s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.23689818382263184s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.02023911476135254s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-slk took 2.8209495544433594s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.24160146713256836s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.24317288398742676s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.482269287109375e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
INFO | --- Analysis for omwn-slv took 2.8888001441955566s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.21286487579345703s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2568528652191162s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020259857177734375s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-swe took 2.897193431854248s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.2298126220703125s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2709817886352539s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-tha took 2.9243977069854736s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.856813907623291s
Availability | VoID file availability check for OntoBeef Domain took 0.0007920265197753906s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2644679546356201s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.8160552978515625e-05s
Believability | Calculation of trust value for OntoBeef Domain took 8.58306884765625e-06s
INFO | --- Analysis for ontobeef-domain took 30.853265523910522s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.3392181396484375e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005829334259033203s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.28173327445983887s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.226799011230469e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.152557373046875e-06s
INFO | --- Analysis for ontos-news-portal took 6.1721062660217285s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.291534423828125e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.257066011428833s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.02054142951965332s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.218650817871094e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.867813110351562e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.425769090652466s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0006279945373535156s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2823450565338135s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.838539123535156e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 3.751183271408081s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.506111145019531e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.27993226051330566s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.218650817871094e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 6.67572021484375e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.9486849308013916s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.2438507080078125e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.25228357315063477s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 5.030632019042969e-05s
Believability | Calculation of trust value for Open Data Euskadi took 5.0067901611328125e-06s
INFO | --- Analysis for open-data-euskadi took 8.244745254516602s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 8.440017700195312e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.24451708793640137s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.0001125335693359375s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.867813110351562e-06s
INFO | --- Analysis for open-data-risp took 4.5651702880859375s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.2121737003326416s
Availability | VoID file availability check for Open Data Thesaurus took 0.0006461143493652344s
Extra | Recovery of all triples for Open Data Thesaurus took 1.4413373470306396s
Performance | Total latancy measurement for Open Data Thesaurus took 0.4777693748474121s
Amount of data | Number of triples check for Open Data Thesaurus took 0.1340649127960205s
Interoperability | New terms check for Open Data Thesaurus took 1.2676043510437012s
Versatility | Languages check for Open Data Thesaurus took 0.12985515594482422s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.13116765022277832s
Security | Check HTTPS for Open Data Thesaurus took 0.3469831943511963s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12450981140136719s
Versatility | Serialization formats check for Open Data Thesaurus took 0.11942720413208008s
Availability | RDF dump link check for Open Data Thesaurus took 1.097365379333496s
License | MR license check for Open Data Thesaurus took 0.10369277000427246s
License | HR license check for Open Data Thesaurus took 0.11059856414794922s
Amount of data | Number of property check for Open Data Thesaurus took 0.11543679237365723s
Understandability | Number of label check for Open Data Thesaurus took 0.12857747077941895s
Understandability | URI regex check for Open Data Thesaurus took 0.20629191398620605s
Understandability | Vocabs check for Open Data Thesaurus took 0.14411425590515137s
Verifiability | Authors check for Open Data Thesaurus took 0.11957311630249023s
Verifiability | Publishers check for Open Data Thesaurus took 0.11848139762878418s
Performance | Throughput check for Open Data Thesaurus took 10.369559526443481s
Amount of data | Check the number of entities for Open Data Thesaurus took 7.677078247070312e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.13959050178527832s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.10430169105529785s
Interlinking | skos check for Open Data Thesaurus took 0.11829757690429688s
Interlinking | skos check for Open Data Thesaurus took 0.09554553031921387s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.10203886032104492s
Currency | Creation date check for Open Data Thesaurus took 0.17775630950927734s
Currency | Modification date check for Open Data Thesaurus took 0.24142909049987793s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.42229413986206055s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.12777018547058105s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.08789992332458496s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.1199183464050293s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.2193317413330078s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.0011632442474365234s
Consistency | Disjoint class check for Open Data Thesaurus took 0.10007381439208984s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.17453265190124512s
Consistency | Misplaced classes for Open Data Thesaurus took 0.1071479320526123s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.3200514316558838s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.258042335510254s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001380443572998047s
Security | Sign check for Open Data Thesaurus took 0.07970738410949707s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.3042914867401123s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020110368728637695s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.963180541992188e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for open-data-thesaurus took 66.93234872817993s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2682051658630371s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.8371810913085938e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 6.67572021484375e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.92358660697937s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.506111145019531e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005488395690917969s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.2721223831176758s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020128250122070312s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.699562072753906e-05s
Believability | Calculation of trust value for Open Election Data Project took 4.0531158447265625e-06s
INFO | --- Analysis for open-election-data-project took 5.034661531448364s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 5.765571355819702s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.26875877380371094s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 0.00010156631469726562s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 5.9604644775390625e-06s
INFO | --- Analysis for open-energy-info-wiki took 14.528836965560913s
Availability | SPARQL endpoint availability check for Open Library took 4.291534423828125e-05s
Availability | VoID file availability check for Open Library took 0.0007414817810058594s
Completeness | Calculation of interlinking completeness for Open Library took 0.2547283172607422s
Reputation | Calculation of the PageRank for Open Library took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for Open Library took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Library took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.866455078125e-05s
Believability | Calculation of trust value for Open Library took 6.198883056640625e-06s
INFO | --- Analysis for open-library took 11.010761260986328s
Availability | SPARQL endpoint availability check for Open Directory took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Directory took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2531580924987793s
Reputation | Calculation of the PageRank for Open Directory took 0.020068883895874023s
Interlinking | Calculation of Degree of Connection for Open Directory took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Directory took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Open Directory took 2.86102294921875e-05s
Believability | Calculation of trust value for Open Directory took 1.7642974853515625e-05s
INFO | --- Analysis for open_directory took 2.940082311630249s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.1952991485595703s
Availability | VoID file availability check for Open Land Use @PSNC took 0.00033092498779296875s
Extra | Recovery of all triples for Open Land Use @PSNC took 116.7292628288269s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9603273868560791s
Amount of data | Number of triples check for Open Land Use @PSNC took 8.259755373001099s
Interoperability | New terms check for Open Land Use @PSNC took 12.994492053985596s
Versatility | Languages check for Open Land Use @PSNC took 300.21260833740234s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 3.152296543121338s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.22550201416015625s
Versatility | Serialization formats check for Open Land Use @PSNC took 9.758073568344116s
Availability | RDF dump link check for Open Land Use @PSNC took 0.28145313262939453s
License | MR license check for Open Land Use @PSNC took 0.557706356048584s
License | HR license check for Open Land Use @PSNC took 300.25136518478394s
Amount of data | Number of property check for Open Land Use @PSNC took 0.22222638130187988s
Understandability | Number of label check for Open Land Use @PSNC took 2.8953137397766113s
Understandability | URI regex check for Open Land Use @PSNC took 0.8657989501953125s
Understandability | Vocabs check for Open Land Use @PSNC took 0.47266554832458496s
Verifiability | Authors check for Open Land Use @PSNC took 0.18637537956237793s
Verifiability | Publishers check for Open Land Use @PSNC took 0.27791595458984375s
Performance | Throughput check for Open Land Use @PSNC took 11.525555849075317s
Amount of data | Check the number of entities for Open Land Use @PSNC took 7.414817810058594e-05s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.19890379905700684s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.18156695365905762s
Interlinking | skos check for Open Land Use @PSNC took 0.4511728286743164s
Interlinking | skos check for Open Land Use @PSNC took 0.4418020248413086s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 6.71954870223999s
Currency | Creation date check for Open Land Use @PSNC took 0.49712252616882324s
Currency | Modification date check for Open Land Use @PSNC took 0.23041415214538574s
Rep.Conc. | URIs length for Open Land Use @PSNC took 153.13899970054626s
Interoperability | New vocabularies check for Open Land Use @PSNC took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.19490623474121094s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.2666919231414795s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.2512023448944092s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 42.94002413749695s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.685225486755371s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.603654384613037s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.19518041610717773s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 86.38029861450195s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.49720573425293s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 37.60988140106201s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.2626631259918213s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 82.73299813270569s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.7356553077697754s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.555755615234375s
Security | Sign check for Open Land Use @PSNC took 0.43998241424560547s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 10.333648681640625s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.5142536163330078s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02102375030517578s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 0.00010132789611816406s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 2.384185791015625e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for Open_Land_Use took 2282.8944799900055s
Availability | SPARQL endpoint availability check for flyatlas took 1.7229232788085938s
Availability | VoID file availability check for flyatlas took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for flyatlas took 0.731889009475708s
Reputation | Calculation of the PageRank for flyatlas took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for flyatlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flyatlas took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.24249267578125e-05s
Believability | Calculation of trust value for flyatlas took 6.9141387939453125e-06s
INFO | --- Analysis for openbiomed-flyatlas took 11.348702430725098s
Availability | SPARQL endpoint availability check for OpenCalais took 4.482269287109375e-05s
Availability | VoID file availability check for OpenCalais took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2781963348388672s
Reputation | Calculation of the PageRank for OpenCalais took 0.020344257354736328s
Interlinking | Calculation of Degree of Connection for OpenCalais took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00011181831359863281s
Believability | Calculation of trust value for OpenCalais took 7.152557373046875e-06s
INFO | --- Analysis for opencalais took 6.509225130081177s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.2661592960357666s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.486343383789062e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.0067901611328125e-06s
INFO | --- Analysis for opencorporates took 3.7527050971984863s
Availability | SPARQL endpoint availability check for OpenCyc took 4.3392181396484375e-05s
Availability | VoID file availability check for OpenCyc took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.24655699729919434s
Reputation | Calculation of the PageRank for OpenCyc took 0.02050018310546875s
Interlinking | Calculation of Degree of Connection for OpenCyc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010752677917480469s
Believability | Calculation of trust value for OpenCyc took 7.3909759521484375e-06s
INFO | --- Analysis for opencyc took 2.3717148303985596s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.25989675521850586s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.600120544433594e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.6902074813842773s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.25679898262023926s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.5049564838409424s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.000553131103515625s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.265958309173584s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.391982316970825s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.26929187774658203s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.328136920928955s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2541215419769287s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.4824445247650146s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.935264587402344e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.2565281391143799s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.5762786865234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.456554889678955s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 4.649162292480469e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.29855775833129883s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.3589859008789062e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.5111641883850098s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.601478576660156e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.000385284423828125s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.29908084869384766s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 9.298324584960938e-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.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.3886287212371826s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0011119842529296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.24463343620300293s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.493403911590576s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2544534206390381s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.3957786560058594s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0008728504180908203s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2625095844268799s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.02071547508239746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.379767417907715s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.24016594886779785s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.373842477798462s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.8160552978515625e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.0010976791381835938s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.26618266105651855s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.4878292083740234s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 6.008148193359375e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.25078535079956055s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.02048182487487793s
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.0007371902465820312s
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.3124616146087646s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2696719169616699s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020338058471679688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 1.33514404296875e-05s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.45658540725708s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 8.988380432128906e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.25238561630249023s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020306825637817383s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.5195424556732178s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.001081228256225586s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2876133918762207s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.022085189819335938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0010333061218261719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.839897155761719e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.674557685852051s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0005588531494140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.25403738021850586s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.021825790405273438s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0010416507720947266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.4269802570343018s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 5.7220458984375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007584095001220703s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.27179431915283203s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020262718200683594s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.886222839355469e-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.2424230575561523s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0004191398620605469s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.26114940643310547s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.1484832763671875e-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.4452388286590576s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0010707378387451172s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.24633216857910156s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02059006690979004s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.5542209148406982s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.25316286087036133s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.469364643096924s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 5.221366882324219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.25370097160339355s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.4221343994140625s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.28020715713500977s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020592212677001953s
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.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.586054563522339s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.839897155761719e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0009522438049316406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.25038576126098633s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020537853240966797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.5221526622772217s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2715740203857422s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.461332321166992s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0008447170257568359s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.23319029808044434s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.020334482192993164s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.45070219039917s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.410743713378906e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2679476737976074s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020786285400390625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.267692565917969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.4193472862243652s
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.00040221214294433594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.26328301429748535s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.5225603580474854s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0005803108215332031s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.27060937881469727s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.410743713378906e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.5822906494140625s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.6253204345703125e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2683112621307373s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.50492262840271s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 5.698204040527344e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.26093149185180664s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.5693421363830566s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2688431739807129s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.02165842056274414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 5.1975250244140625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.5362749099731445s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2482619285583496s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.021408796310424805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.887580871582031e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.3891921043395996s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 5.459785461425781e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.25206494331359863s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020707368850708008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.458427429199219e-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.383147954940796s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0005805492401123047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.24378466606140137s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02027416229248047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.792213439941406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.4837026596069336s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.26576805114746094s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02077651023864746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.5299530029296875e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.523616075515747s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.2694211006164551s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.5299530029296875e-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 2.5705747604370117s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0005595684051513672s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.24852228164672852s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.020455598831176758s
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.0008227825164794922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.5209739208221436s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0010099411010742188s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.26834750175476074s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.696846008300781e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.465606451034546s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 5.888938903808594e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.26784777641296387s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.743171691894531e-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 2.3993189334869385s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.2681140899658203s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.505154609680176s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.5299530029296875e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.2631845474243164s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020283222198486328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 9.059906005859375e-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.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.4254813194274902s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 3.524974822998047s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.28964996337890625s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.0203857421875s
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.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.749961853027344e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 6.9141387939453125e-06s
INFO | --- Analysis for opendataec took 8.164451837539673s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 5.650520324707031e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005424022674560547s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.27500343322753906s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.023270606994629s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.258455753326416s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.589414596557617s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.24998855590820312s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 6.198883056640625e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 3.761204481124878s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.27982401847839355s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 3.73537278175354s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.410743713378906e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005981922149658203s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.28937697410583496s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.020803213119506836s
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.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 3.5544283390045166s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 9.34600830078125e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005826950073242188s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2611513137817383s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0008018016815185547s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.601478576660156e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 3.696521282196045s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.25510144233703613s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 9.298324584960938e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 3.8054659366607666s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.601478576660156e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2700645923614502s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 3.729660749435425s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2560453414916992s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020589828491210938s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.2878835201263428s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.38102436065674s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.28593993186950684s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.022545814514160156s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 7.152557373046875e-06s
INFO | --- Analysis for openlink-lod-cache took 62.91071271896362s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.887580871582031e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.000457763671875s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.2803473472595215s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.584426879882812e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 7.152557373046875e-06s
INFO | --- Analysis for openlinksw-dataspaces took 2.983745813369751s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.315376281738281e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.23914408683776855s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020254135131835938s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.250640869140625e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 4.5299530029296875e-06s
INFO | --- Analysis for openlylocal took 10.370262145996094s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 0.8472268581390381s
Availability | VoID file availability check for OpenMobileNetwork took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2633366584777832s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02081751823425293s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.0108642578125e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 8.58306884765625e-06s
INFO | --- Analysis for openmobilenetwork took 3.809906005859375s
Availability | SPARQL endpoint availability check for OpenTox took 4.076957702636719e-05s
Availability | VoID file availability check for OpenTox took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for OpenTox took 0.27559852600097656s
Reputation | Calculation of the PageRank for OpenTox took 0.020958900451660156s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.361701965332031e-05s
Believability | Calculation of trust value for OpenTox took 6.67572021484375e-06s
INFO | --- Analysis for opentox took 2.9565324783325195s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.363059997558594e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.25983285903930664s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02074408531188965s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.266334533691406e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.867813110351562e-06s
INFO | --- Analysis for openuplabs took 2.9874157905578613s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.1961669921875e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.28048110008239746s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.02091526985168457s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.218650817871094e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 8.344650268554688e-06s
INFO | --- Analysis for opus took 2.929429531097412s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 5.435943603515625e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0002961158752441406s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2783973217010498s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.933906555175781e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 9.775161743164062e-06s
INFO | --- Analysis for orcid took 2.861467123031616s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.2124509811401367s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006682872772216797s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.25300025939941406s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020717382431030273s
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.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.00010371208190917969s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.575353384017944s
Availability | SPARQL endpoint availability check for oreilly took 4.744529724121094e-05s
Availability | VoID file availability check for oreilly took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for oreilly took 0.24503803253173828s
Reputation | Calculation of the PageRank for oreilly took 0.020763635635375977s
Interlinking | Calculation of Degree of Connection for oreilly took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for oreilly took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.1021575927734375e-05s
Believability | Calculation of trust value for oreilly took 1.2636184692382812e-05s
INFO | --- Analysis for oreilly took 5.096568822860718s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.4208779335021973s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.25321340560913086s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.337860107421875e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 6.67572021484375e-06s
INFO | --- Analysis for Organchem-Data took 7.234753608703613s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.10087442398071289s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2964797019958496s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020592451095581055s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 7.128715515136719e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for organic-edunet took 10.28489899635315s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.4819626808166504s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0006284713745117188s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 12.498446226119995s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.8563742637634277s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.1940631866455078s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.5320367813110352s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 7.536644458770752s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.19757628440856934s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.42927074432373047s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.14406991004943848s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.1653299331665039s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.17069649696350098s
License | HR license check for Open Research Knowledge Graph (ORKG) took 4.7065348625183105s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.1493079662322998s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.2874748706817627s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.3468616008758545s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.15852093696594238s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.19268178939819336s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.18658709526062012s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.876808166503906s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 7.605552673339844e-05s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.14496254920959473s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.17583346366882324s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.18997764587402344s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.6654212474822998s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.1573784351348877s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.37370848655700684s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.38955092430114746s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 7.038511037826538s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.13710713386535645s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.17322754859924316s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.21561789512634277s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 7.621534824371338s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.25948071479797363s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.2775890827178955s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.2678067684173584s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.5892853736877441s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.9171674251556396s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 5.46497917175293s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.1922099590301514s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.1651742458343506s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.28223752975463867s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.17113304138183594s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.15025925636291504s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2099.59876203537s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.6713593006134033s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.020822763442993164s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.1205673217773438e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 7.867813110351562e-06s
INFO | --- Analysis for orkg took 2385.2136602401733s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 3.0273842811584473s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2729184627532959s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.368492126464844e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 7.152557373046875e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 30.71889019012451s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.6498312950134277s
Availability | VoID file availability check for OSM Semantic Network took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.26803159713745117s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.504753112792969e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.62939453125e-06s
INFO | --- Analysis for osm-semantic-network took 9.193493366241455s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.49263787269592285s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.000301361083984375s
Extra | Recovery of all triples for Open Transport Map @PSNC took 121.29523992538452s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.9487504959106445s
Amount of data | Number of triples check for Open Transport Map @PSNC took 8.181101322174072s
Interoperability | New terms check for Open Transport Map @PSNC took 14.915965557098389s
Versatility | Languages check for Open Transport Map @PSNC took 300.2322874069214s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 3.0020759105682373s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.23755860328674316s
Versatility | Serialization formats check for Open Transport Map @PSNC took 11.103001832962036s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.24675464630126953s
License | MR license check for Open Transport Map @PSNC took 0.48483824729919434s
License | HR license check for Open Transport Map @PSNC took 300.243768453598s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.3725929260253906s
Understandability | Number of label check for Open Transport Map @PSNC took 3.1041619777679443s
Understandability | URI regex check for Open Transport Map @PSNC took 0.9069533348083496s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.45192837715148926s
Verifiability | Authors check for Open Transport Map @PSNC took 0.21269869804382324s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.2784907817840576s
Performance | Throughput check for Open Transport Map @PSNC took 11.35318636894226s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 8.225440979003906e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.18300342559814453s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.22217774391174316s
Interlinking | skos check for Open Transport Map @PSNC took 0.48568224906921387s
Interlinking | skos check for Open Transport Map @PSNC took 0.42711663246154785s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 6.13724946975708s
Currency | Creation date check for Open Transport Map @PSNC took 0.5168354511260986s
Currency | Modification date check for Open Transport Map @PSNC took 0.23494553565979004s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 156.0902705192566s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.20020508766174316s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.38024187088012695s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.3494069576263428s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 40.340479373931885s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6816205978393555s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.660907745361328s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.19470763206481934s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 83.29783868789673s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.478052377700806s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 35.69969201087952s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.2157282829284668s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 81.83586120605469s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.765143632888794s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.581315279006958s
Security | Sign check for Open Transport Map @PSNC took 0.8702387809753418s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 10.189017057418823s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.8868772983551025s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 3.504753112792969e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.62939453125e-06s
INFO | --- Analysis for OTM took 2242.361948490143s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 7.271766662597656e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.6921586990356445s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020908355712890625s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 8.106231689453125e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 5.211129188537598s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.267692565917969e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.24789047241210938s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.075599670410156e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.8126420974731445s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.410743713378906e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.6958432197570801s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.0517578125e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.326446771621704s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.291534423828125e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.7026708126068115s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 1.33514404296875e-05s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.800568103790283s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 5.435943603515625e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.2711606025695801s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.86102294921875e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 6.67572021484375e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.42250919342041s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.267692565917969e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.2607603073120117s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020960330963134766s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0008380413055419922s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.982781171798706s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.2438507080078125e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2689025402069092s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020668506622314453s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.528594970703125e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 8.106231689453125e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.942004919052124s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.124641418457031e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.27916550636291504s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020287036895751953s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 6.9141387939453125e-06s
INFO | --- Analysis for oxpoints took 2.950406551361084s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.9365856647491455s
Availability | VoID file availability check for Pali English Lexicon took 0.0006005764007568359s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.24406123161315918s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020220518112182617s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.956390380859375e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.152557373046875e-06s
INFO | --- Analysis for pali-english-lexicon took 7.367113351821899s
Availability | SPARQL endpoint availability check for PanLex took 0.47126150131225586s
Availability | VoID file availability check for PanLex took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for PanLex took 0.2789618968963623s
Reputation | Calculation of the PageRank for PanLex took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for PanLex took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PanLex took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.2479248046875e-05s
Believability | Calculation of trust value for PanLex took 7.3909759521484375e-06s
INFO | --- Analysis for panlex took 2.894261598587036s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.267692565917969e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.28111743927001953s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020886898040771484s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 4.1961669921875e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 5.4836273193359375e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.842121839523315s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.07767271995544434s
Availability | VoID file availability check for patents.data.gov.uk took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2605400085449219s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020635128021240234s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 5.1021575927734375e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 6.67572021484375e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.5769622325897217s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 5.0067901611328125e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0006101131439208984s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.27061891555786133s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.00090789794921875s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 4.1961669921875e-05s
Believability | Calculation of trust value for PDEV-Lemon took 6.67572021484375e-06s
INFO | --- Analysis for pdev-lemon took 4.02044939994812s
Availability | SPARQL endpoint availability check for pdevlemon took 4.2438507080078125e-05s
Availability | VoID file availability check for pdevlemon took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.28472018241882324s
Reputation | Calculation of the PageRank for pdevlemon took 0.02033090591430664s
Interlinking | Calculation of Degree of Connection for pdevlemon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.6941299438476562e-05s
Believability | Calculation of trust value for pdevlemon took 6.9141387939453125e-06s
INFO | --- Analysis for pdevlemon took 3.0887248516082764s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 6.604194641113281e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2601301670074463s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.772445678710938e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 6.67572021484375e-06s
INFO | --- Analysis for periodo took 21.378811359405518s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.315376281738281e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2601490020751953s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00039315223693847656s
Believability | Calculation of trust value for Personal_Homepages took 7.152557373046875e-06s
INFO | --- Analysis for personal-homepages took 2.3927087783813477s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.315376281738281e-05s
Availability | VoID file availability check for Ontology of University People took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2587771415710449s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020633935928344727s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.8371810913085938e-05s
Believability | Calculation of trust value for Ontology of University People took 1.33514404296875e-05s
INFO | --- Analysis for PersonOnto took 2.3159842491149902s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.873519659042358s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.28774118423461914s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02024245262145996s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0967254638671875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.152557373046875e-06s
INFO | --- Analysis for PFKHS took 13.45909333229065s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 3.5670831203460693s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.000316619873046875s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.24743270874023438s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0728836059570312e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.67572021484375e-06s
INFO | --- Analysis for PFRPPH took 9.720708131790161s
Availability | SPARQL endpoint availability check for PGxLOD took 0.41807103157043457s
Availability | VoID file availability check for PGxLOD took 0.0005774497985839844s
Extra | Recovery of all triples for PGxLOD took 2.3848748207092285s
Performance | Total latancy measurement for PGxLOD took 1.040457010269165s
Amount of data | Number of triples check for PGxLOD took 3.5308244228363037s
Interoperability | New terms check for PGxLOD took 1.8492398262023926s
Versatility | Languages check for PGxLOD took 60.257267475128174s
Interpretability | Number of blank nodes check for PGxLOD took 1.5984811782836914s
Interpretability | RDF structures check for PGxLOD took 0.5602009296417236s
Versatility | Serialization formats check for PGxLOD took 0.37600016593933105s
Availability | RDF dump link check for PGxLOD took 53.99444365501404s
License | MR license check for PGxLOD took 0.919722318649292s
License | HR license check for PGxLOD took 64.36675572395325s
Amount of data | Number of property check for PGxLOD took 0.16108942031860352s
Understandability | Number of label check for PGxLOD took 3.069350242614746s
Understandability | URI regex check for PGxLOD took 0.4294865131378174s
Understandability | Vocabs check for PGxLOD took 0.3372063636779785s
Verifiability | Authors check for PGxLOD took 0.38359665870666504s
Verifiability | Publishers check for PGxLOD took 0.3157346248626709s
Performance | Throughput check for PGxLOD took 10.757033824920654s
Amount of data | Check the number of entities for PGxLOD took 0.11891698837280273s
Verifiability | Contribs. check for PGxLOD took 0.15546941757202148s
Interlinking | sameAs chians check for PGxLOD took 0.26509857177734375s
Interlinking | skos check for PGxLOD took 1.5717763900756836s
Interlinking | skos check for PGxLOD took 0.20095133781433105s
Timeliness | dataset update frequency check for PGxLOD took 0.37073826789855957s
Currency | Creation date check for PGxLOD took 0.5273036956787109s
Currency | Modification date check for PGxLOD took 0.3634214401245117s
Rep.Conc. | URIs length for PGxLOD took 7.390296936035156s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.18456172943115234s
Accuracy | Check Functional Property for PGxLOD took 0.21109294891357422s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.1829078197479248s
Accuracy | Check Empty annotation labels for PGxLOD took 1.159623622894287s
Accuracy | Check White space in annotation for PGxLOD took 0.03765439987182617s
Accuracy | Check Datatype consistency for PGxLOD took 0.027957916259765625s
Consistency | Disjoint class check for PGxLOD took 0.2899343967437744s
Consistency | Check Misplaced properties for PGxLOD took 6.8453545570373535s
Consistency | Misplaced classes for PGxLOD took 0.28397536277770996s
Consistency | Check Ontology hijacking for PGxLOD took 2.24092698097229s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.1217749118804932s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.30511474609375s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03131580352783203s
Conciseness | Check Intensional conciseness for PGxLOD took 0.3089480400085449s
Security | Sign check for PGxLOD took 0.19338083267211914s
Availability | Check URIs Dereferenciability for PGxLOD took 1687.760407924652s
Completeness | Calculation of interlinking completeness for PGxLOD took 1.1145827770233154s
Reputation | Calculation of the PageRank for PGxLOD took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 6.723403930664062e-05s
Believability | Calculation of trust value for PGxLOD took 6.9141387939453125e-06s
INFO | --- Analysis for PGxLOD took 3062.444355249405s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.1594371795654297s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.7232973575592041s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.62396240234375e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 8.106231689453125e-06s
INFO | --- Analysis for phoible took 7.145138263702393s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 7.748603820800781e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.24076581001281738s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 2.86102294921875e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 6.9141387939453125e-06s
INFO | --- Analysis for PISM took 18.76677370071411s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.3392181396484375e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.26383137702941895s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020386219024658203s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.368492126464844e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.152557373046875e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.379077434539795s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.9579341411590576s
Availability | VoID file availability check for digitized plant specimen took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.6887421607971191s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0008411407470703125s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.724761962890625e-05s
Believability | Calculation of trust value for digitized plant specimen took 7.152557373046875e-06s
INFO | --- Analysis for plant-specimen took 4.741726636886597s
Availability | SPARQL endpoint availability check for Pleiades took 4.220008850097656e-05s
Availability | VoID file availability check for Pleiades took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Pleiades took 0.26021718978881836s
Reputation | Calculation of the PageRank for Pleiades took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for Pleiades took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.249282836914062e-05s
Believability | Calculation of trust value for Pleiades took 6.4373016357421875e-06s
INFO | --- Analysis for pleiades took 16.41605544090271s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.2438507080078125e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.26909351348876953s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.021225929260253906s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.528594970703125e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.62939453125e-06s
INFO | --- Analysis for podorozhnyk took 13.968064785003662s
Availability | SPARQL endpoint availability check for Poképédia took 4.267692565917969e-05s
Availability | VoID file availability check for Poképédia took 0.0006310939788818359s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2669506072998047s
Reputation | Calculation of the PageRank for Poképédia took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for Poképédia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.295608520507812e-05s
Believability | Calculation of trust value for Poképédia took 7.152557373046875e-06s
INFO | --- Analysis for pokepedia-fr took 2.650669574737549s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.4345855712890625e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0013034343719482422s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2767512798309326s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.653236389160156e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.152557373046875e-06s
INFO | --- Analysis for polymath-virtual-library took 5.762979984283447s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.5066478252410889s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.2660529613494873s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.1444091796875e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.867813110351562e-06s
INFO | --- Analysis for portuguese_prisons_releases took 5.798151254653931s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.3392181396484375e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.26082897186279297s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0008442401885986328s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.504753112792969e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.899376392364502s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 5.269050598144531e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2586100101470947s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.0202634334564209s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.86102294921875e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.9243648052215576s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 5.173683166503906e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.26125597953796387s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.24249267578125e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 5.7220458984375e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.9984066486358643s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.100799560546875e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.262526273727417s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 2.8848648071289062e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.963414430618286s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2595498561859131s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.0204007625579834s
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.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.765655517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 5.9604644775390625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 3.0133399963378906s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.279461145401001s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 6.198883056640625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.9030323028564453s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.00023365020751953125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.26885557174682617s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.919536828994751s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.2716081142425537s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.9505505561828613s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.26484012603759766s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 5.9604644775390625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.974693775177002s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 6.246566772460938e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2990586757659912s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.0279159545898438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 6.198883056640625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.954728603363037s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.2438507080078125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.25473713874816895s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020404577255249023s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 6.198883056640625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.9140610694885254s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.9591064453125e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.2590157985687256s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.9765422344207764s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.28537702560424805s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.909743309020996s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2607588768005371s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.870060920715332s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.5299530029296875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2504580020904541s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.075599670410156e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.863415002822876s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.220008850097656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.000362396240234375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.26180267333984375s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020955324172973633s
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.0008819103240966797s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.528594970703125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.917703628540039s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 9.059906005859375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.2798190116882324s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.00072479248046875s
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 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 3.0231287479400635s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.2694089412689209s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.020359039306640625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0009026527404785156s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.743171691894531e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 7.152557373046875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.954056739807129s
Availability | SPARQL endpoint availability check for prefix.cc took 4.3392181396484375e-05s
Availability | VoID file availability check for prefix.cc took 0.0005235671997070312s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.31955814361572266s
Reputation | Calculation of the PageRank for prefix.cc took 0.020365238189697266s
Interlinking | Calculation of Degree of Connection for prefix.cc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.647804260253906e-05s
Believability | Calculation of trust value for prefix.cc took 8.821487426757812e-06s
INFO | --- Analysis for prefix-cc took 3.2835257053375244s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 2.0544228553771973s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.25534605979919434s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.02013397216796875s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.6253204345703125e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.049041748046875e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 8.78565239906311s
Availability | SPARQL endpoint availability check for PreLex took 4.622328042984009s
Availability | VoID file availability check for PreLex took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for PreLex took 0.2739248275756836s
Reputation | Calculation of the PageRank for PreLex took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for PreLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PreLex took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.557868957519531e-05s
Believability | Calculation of trust value for PreLex took 7.62939453125e-06s
INFO | --- Analysis for prelex took 12.821742534637451s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.4529407024383545s
Availability | VoID file availability check for Prelinger Archives took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.2779552936553955s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.075599670410156e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.3909759521484375e-06s
INFO | --- Analysis for prelinger_archives took 12.093560695648193s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.9038939476013184s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.2729029655456543s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007424354553222656s
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 7.152557373046875e-06s
INFO | --- Analysis for premon took 5.881302118301392s
Availability | SPARQL endpoint availability check for Previsible took 4.3392181396484375e-05s
Availability | VoID file availability check for Previsible took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Previsible took 0.29604196548461914s
Reputation | Calculation of the PageRank for Previsible took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Previsible took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.0967254638671875e-05s
Believability | Calculation of trust value for Previsible took 9.5367431640625e-06s
INFO | --- Analysis for Previsible took 2.4322807788848877s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.9114227294921875e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2629208564758301s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 6.604194641113281e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 6.67572021484375e-06s
INFO | --- Analysis for princeton-library-findingaids took 3.5359110832214355s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.46892333030700684s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.2771952152252197s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 6.198883056640625e-06s
INFO | --- Analysis for PrinParLat took 4.1291749477386475s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.36661767959594727s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.28670501708984375s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.02027297019958496s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.0108642578125e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 6.67572021484375e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.322640895843506s
Availability | SPARQL endpoint availability check for Prior Panel took 4.1961669921875e-05s
Availability | VoID file availability check for Prior Panel took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.2699284553527832s
Reputation | Calculation of the PageRank for Prior Panel took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.266334533691406e-05s
Believability | Calculation of trust value for Prior Panel took 5.4836273193359375e-06s
INFO | --- Analysis for Prior_Panel took 2.3902206420898438s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.76837158203125e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.26334261894226074s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020298242568969727s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.9325485229492188e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 6.198883056640625e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.8777880668640137s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.1961669921875e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.2614307403564453s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.02021169662475586s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.0994415283203125e-05s
Believability | Calculation of trust value for Procomún SPARQL took 5.9604644775390625e-06s
INFO | --- Analysis for procomun-sparql took 2.9233603477478027s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.267692565917969e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.25261926651000977s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020168781280517578s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 2.7894973754882812e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.907693862915039s
Availability | SPARQL endpoint availability check for ProductDB took 1.986509084701538s
Availability | VoID file availability check for ProductDB took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2787196636199951s
Reputation | Calculation of the PageRank for ProductDB took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for ProductDB took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ProductDB took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.414817810058594e-05s
Believability | Calculation of trust value for ProductDB took 1.049041748046875e-05s
INFO | --- Analysis for productdb took 5.709945201873779s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.260059118270874s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 8.320808410644531e-05s
Believability | Calculation of trust value for Product Types Ontology took 6.198883056640625e-06s
INFO | --- Analysis for productontology took 3.5935893058776855s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.1484832763671875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.2570021152496338s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.00010156631469726562s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 6.4373016357421875e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 4.697715997695923s
Availability | SPARQL endpoint availability check for provenanceweb took 0.057154178619384766s
Availability | VoID file availability check for provenanceweb took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.28828978538513184s
Reputation | Calculation of the PageRank for provenanceweb took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for provenanceweb took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.915496826171875e-05s
Believability | Calculation of trust value for provenanceweb took 7.867813110351562e-06s
INFO | --- Analysis for provenanceweb took 66.12516689300537s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.267692565917969e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2701258659362793s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010085105895996094s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 6.9141387939453125e-06s
INFO | --- Analysis for proyectoapadrina took 4.475193977355957s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.537826776504517s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008099079132080078s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2849736213684082s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020792007446289062s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.314018249511719e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 5.245208740234375e-06s
INFO | --- Analysis for pscs-catalogue took 125.93076467514038s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.220008850097656e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.0003905296325683594s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.28174424171447754s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 8.249282836914062e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 6.9141387939453125e-06s
INFO | --- Analysis for psh-subject-headings took 2.834158420562744s
Availability | SPARQL endpoint availability check for Depression took 0.3570973873138428s
Availability | VoID file availability check for Depression took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Depression took 0.267366886138916s
Reputation | Calculation of the PageRank for Depression took 0.02038860321044922s
Interlinking | Calculation of Degree of Connection for Depression took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Depression took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Depression took 2.8371810913085938e-05s
Believability | Calculation of trust value for Depression took 6.4373016357421875e-06s
INFO | --- Analysis for Psychology took 2.750033140182495s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.220008850097656e-05s
Availability | VoID file availability check for PubChem RDF took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.31265926361083984s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.1484832763671875e-05s
Believability | Calculation of trust value for PubChem RDF took 1.0967254638671875e-05s
INFO | --- Analysis for PubChem_RDF took 5.13206148147583s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.267692565917969e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2618422508239746s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.02068352699279785s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.266334533691406e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.152557373046875e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.9036176204681396s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.6998419761657715s
Availability | VoID file availability check for Public Spending in Greece took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.27582216262817383s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.987022399902344e-05s
Believability | Calculation of trust value for Public Spending in Greece took 6.67572021484375e-06s
INFO | --- Analysis for public-spending-in-greece took 8.787611722946167s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.38690185546875e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.26062989234924316s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.765655517578125e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 6.9141387939453125e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.996476650238037s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.2234482765197754s
Availability | VoID file availability check for Publications Office Authority tables took 0.0005474090576171875s
Extra | Recovery of all triples for Publications Office Authority tables took 94.37552118301392s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6192741394042969s
Amount of data | Number of triples check for Publications Office Authority tables took 98.48443412780762s
Interoperability | New terms check for Publications Office Authority tables took 92.54594826698303s
Versatility | Languages check for Publications Office Authority tables took 300.0522315502167s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 1.4772908687591553s
Security | Check HTTPS for Publications Office Authority tables took 0.3324546813964844s
Interpretability | RDF structures check for Publications Office Authority tables took 0.3198542594909668s
Versatility | Serialization formats check for Publications Office Authority tables took 3.4024498462677s
Availability | RDF dump link check for Publications Office Authority tables took 0.21134328842163086s
License | MR license check for Publications Office Authority tables took 0.26714181900024414s
License | HR license check for Publications Office Authority tables took 300.09681510925293s
Amount of data | Number of property check for Publications Office Authority tables took 0.1665506362915039s
Understandability | Number of label check for Publications Office Authority tables took 6.128523349761963s
Understandability | URI regex check for Publications Office Authority tables took 0.2510948181152344s
Understandability | Vocabs check for Publications Office Authority tables took 0.09745192527770996s
Verifiability | Authors check for Publications Office Authority tables took 0.11997747421264648s
Verifiability | Publishers check for Publications Office Authority tables took 0.16739702224731445s
Performance | Throughput check for Publications Office Authority tables took 10.658215522766113s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.724761962890625e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.11300539970397949s
Interlinking | sameAs chians check for Publications Office Authority tables took 12.596141815185547s
Interlinking | skos check for Publications Office Authority tables took 0.26142430305480957s
Interlinking | skos check for Publications Office Authority tables took 0.26180243492126465s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.24957752227783203s
Currency | Creation date check for Publications Office Authority tables took 0.8330626487731934s
Currency | Modification date check for Publications Office Authority tables took 0.24290895462036133s
Rep.Conc. | URIs length for Publications Office Authority tables took 466.53322434425354s
Interoperability | New vocabularies check for Publications Office Authority tables took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.17795467376708984s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.14800524711608887s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.16241693496704102s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 32.72950744628906s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.1182756423950195s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.625089168548584s
Consistency | Disjoint class check for Publications Office Authority tables took 0.13189029693603516s
Consistency | Check Misplaced properties for Publications Office Authority tables took 300.3850426673889s
Consistency | Misplaced classes for Publications Office Authority tables took 8.404005527496338s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 32.78752875328064s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.410839319229126s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 301.3697545528412s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 2.999309539794922s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.45268964767456055s
Security | Sign check for Publications Office Authority tables took 0.14488959312438965s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 4.185550212860107s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.6459670066833496s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.029273986816406e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.430511474609375e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 6.198883056640625e-06s
INFO | --- Analysis for publications_office_authority_tables took 16019.37228178978s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 7.867813110351562e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.26474690437316895s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.123283386230469e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 6.9141387939453125e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 5.222240924835205s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.363059997558594e-05s
Availability | VoID file availability check for QBOAirbase took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.7293007373809814s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020697355270385742s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.867813110351562e-05s
Believability | Calculation of trust value for QBOAirbase took 7.3909759521484375e-06s
INFO | --- Analysis for qboairbase took 138.23860669136047s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.076957702636719e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.000244140625s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.24846911430358887s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.0040740966796875e-05s
Believability | Calculation of trust value for qualitywebdata.org took 6.9141387939453125e-06s
INFO | --- Analysis for qualitywebdata-org took 3.3429999351501465s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.38690185546875e-05s
Availability | VoID file availability check for Qualité de l'air took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.26284050941467285s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020401716232299805s
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.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.9802322387695312e-05s
Believability | Calculation of trust value for Qualité de l'air took 7.867813110351562e-06s
INFO | --- Analysis for Qualité_de_l'air took 3.6099798679351807s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.291534423828125e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0007739067077636719s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 1.484370231628418s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 3.886222839355469e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.1444091796875e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 1317.1568417549133s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.48119688034057617s
Availability | VoID file availability check for Querolus in LiLa took 0.0006766319274902344s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.27434515953063965s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for Querolus took 6.182047367095947s
Availability | SPARQL endpoint availability check for Quotations Book took 4.291534423828125e-05s
Availability | VoID file availability check for Quotations Book took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2510192394256592s
Reputation | Calculation of the PageRank for Quotations Book took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for Quotations Book took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 2.86102294921875e-05s
Believability | Calculation of trust value for Quotations Book took 1.2159347534179688e-05s
INFO | --- Analysis for quotations_book took 4.278371334075928s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2608199119567871s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020312786102294922s
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.0007245540618896484s
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.3909759521484375e-06s
INFO | --- Analysis for r4r took 2.8785717487335205s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7501180171966553s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7043099403381348s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.38690185546875e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.9141387939453125e-06s
INFO | --- Analysis for racai-legalnero took 5.3292670249938965s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.1961669921875e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.27692556381225586s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020509958267211914s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.075599670410156e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.9567711353302s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 2.1580612659454346s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0003437995910644531s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.24933767318725586s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.0279159545898438e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 7.3909759521484375e-06s
INFO | --- Analysis for racai-llod-parseme-ro took 5.10891318321228s
Availability | SPARQL endpoint availability check for RoLEX took 1.897475242614746s
Availability | VoID file availability check for RoLEX took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for RoLEX took 0.25479888916015625s
Reputation | Calculation of the PageRank for RoLEX took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for RoLEX took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RoLEX took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.814697265625e-05s
Believability | Calculation of trust value for RoLEX took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-rolex took 4.949321269989014s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.3392181396484375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.26611328125s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020236730575561523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.9087066650390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.6417462825775146s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.220008850097656e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.25980162620544434s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.8848648071289062e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 6.198883056640625e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 3.000761032104492s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.2438507080078125e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.2746744155883789s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.0040740966796875e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 6.67572021484375e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.5358128547668457s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 5.8650970458984375e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2739882469177246s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 3.218650817871094e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.6668879985809326s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.4145932197570801s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0012919902801513672s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.2657656669616699s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 2.9087066650390625e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 8.821487426757812e-06s
INFO | --- Analysis for racai-llod-rtasc took 4.064533472061157s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.5138003826141357s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.2745058536529541s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.0201265811920166s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 2.956390380859375e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 7.867813110351562e-06s
INFO | --- Analysis for racai-llod-simonero took 3.5960772037506104s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.2423417568206787s
Availability | VoID file availability check for Rådata nå! took 0.0005624294281005859s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.29647040367126465s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020175933837890625s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.225440979003906e-05s
Believability | Calculation of trust value for Rådata nå! took 1.2159347534179688e-05s
INFO | --- Analysis for radatana took 4.500645875930786s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 5.7220458984375e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0006732940673828125s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.2870931625366211s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007450580596923828s
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 6.198883056640625e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 16.669938564300537s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 3.981590270996094e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.26781797409057617s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 2.86102294921875e-05s
Believability | Calculation of trust value for Raphael Research Resource took 6.4373016357421875e-06s
INFO | --- Analysis for raphaelresearchresource took 2.9331440925598145s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 11.973885536193848s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0005767345428466797s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2719111442565918s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.3855438232421875e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.867813110351562e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 54.3668999671936s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 393.3430905342102s
Availability | VoID file availability check for Polish LGU financial statements took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.316084623336792s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.02121710777282715s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.1948089599609375e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 6.9141387939453125e-06s
INFO | --- Analysis for Rb_PL_LGU took 668.2953543663025s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.673004150390625e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.7540984153747559s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.814697265625e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 6.26363205909729s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.7159876823425293s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.4332275390625e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 5.239161729812622s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.28612399101257324s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.02074575424194336s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 3.8809845447540283s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.458427429199219e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.2617032527923584s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007195472717285156s
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 5.7220458984375e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 3.436739206314087s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 5.650520324707031e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.28255653381347656s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020941495895385742s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.123283386230469e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 6.67572021484375e-06s
INFO | --- Analysis for rcahmw-periods-list took 3.0335693359375s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.267692565917969e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.27712512016296387s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020351886749267578s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.654594421386719e-05s
Believability | Calculation of trust value for RDF Book Mashup took 7.152557373046875e-06s
INFO | --- Analysis for rdf-book-mashup took 3.672391891479492s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.673004150390625e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.2705063819885254s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00012564659118652344s
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.9284183979034424s
Availability | SPARQL endpoint availability check for RDFLicense took 260.5772454738617s
Availability | VoID file availability check for RDFLicense took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.2808208465576172s
Reputation | Calculation of the PageRank for RDFLicense took 0.020956754684448242s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.7670135498046875e-05s
Believability | Calculation of trust value for RDFLicense took 9.059906005859375e-06s
INFO | --- Analysis for rdflicense took 535.5669243335724s
Availability | SPARQL endpoint availability check for RDFohloh took 4.9591064453125e-05s
Availability | VoID file availability check for RDFohloh took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.9473526477813721s
Reputation | Calculation of the PageRank for RDFohloh took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 0.00010156631469726562s
Believability | Calculation of trust value for RDFohloh took 6.9141387939453125e-06s
INFO | --- Analysis for rdfohloh took 7.404846668243408s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.5829372406005859s
Availability | VoID file availability check for Reactome RDF took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.28172779083251953s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for Reactome RDF took 8.344650268554688e-06s
INFO | --- Analysis for reactome-rdf took 4.088014602661133s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 3.575072765350342s
Availability | VoID file availability check for Rechtspraak.nl took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.7157571315765381s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020763635635375977s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.72747802734375e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 1.0013580322265625e-05s
INFO | --- Analysis for rechtspraak took 10.430221796035767s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.3392181396484375e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.27431774139404297s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 9.322166442871094e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 1.2874603271484375e-05s
INFO | --- Analysis for red-uno-internacional-santillana took 7.597864627838135s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.09497857093811035s
Availability | VoID file availability check for reference.data.gov.uk took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.26293087005615234s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00016379356384277344s
Believability | Calculation of trust value for reference.data.gov.uk took 5.7220458984375e-06s
INFO | --- Analysis for reference-data-gov-uk took 3.078422784805298s
Availability | SPARQL endpoint availability check for Regiony took 4.220008850097656e-05s
Availability | VoID file availability check for Regiony took 0.0006194114685058594s
Completeness | Calculation of interlinking completeness for Regiony took 0.30199193954467773s
Reputation | Calculation of the PageRank for Regiony took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Regiony took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.1948089599609375e-05s
Believability | Calculation of trust value for Regiony took 8.344650268554688e-06s
INFO | --- Analysis for regiony took 2.951831579208374s
Availability | SPARQL endpoint availability check for RELD took 262.11170506477356s
Availability | VoID file availability check for RELD took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for RELD took 0.8112077713012695s
Reputation | Calculation of the PageRank for RELD took 0.02108907699584961s
Interlinking | Calculation of Degree of Connection for RELD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for RELD took 4.0531158447265625e-05s
Believability | Calculation of trust value for RELD took 5.9604644775390625e-06s
INFO | --- Analysis for RELD took 536.8539493083954s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.21002531051635742s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005753040313720703s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.8738107681274414s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.5995321273803711s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.694169282913208s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.623518705368042s
Versatility | Languages check for Repository for Linked Open Archival Data took 6.5953688621521s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.2340970039367676s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.20383334159851074s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.3275489807128906s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.2571239471435547s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.20868921279907227s
License | MR license check for Repository for Linked Open Archival Data took 0.47188615798950195s
License | HR license check for Repository for Linked Open Archival Data took 8.50912356376648s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.19185328483581543s
Understandability | Number of label check for Repository for Linked Open Archival Data took 0.9205427169799805s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.46613264083862305s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.14755582809448242s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.23165512084960938s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.2479724884033203s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.448453903198242s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.00011491775512695312s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.14973664283752441s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.2100391387939453s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.20965242385864258s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.1523427963256836s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.3027229309082031s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.469494104385376s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.2654449939727783s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 2.844438314437866s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.17925596237182617s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.09653782844543457s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.16640210151672363s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 0.6296103000640869s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.02933049201965332s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028208255767822266s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.25833868980407715s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.128358840942383s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.2804849147796631s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.573767900466919s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.125204086303711s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.187103033065796s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.029821395874023438s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.21038031578063965s
Security | Sign check for Repository for Linked Open Archival Data took 0.49349403381347656s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 2514.9119181632996s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 1.579223871231079s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.021376371383666992s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 0.00011301040649414062s
Interoperability | Check the re-using of existing vocabs for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 9.5367431640625e-06s
INFO | --- Analysis for reload took 2632.035824775696s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.506111145019531e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0007479190826416016s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.7411825656890869s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for Land use merced dataset took 6.67572021484375e-06s
INFO | --- Analysis for remote_Sensing took 15.41421627998352s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.8195652961730957s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.26317358016967773s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 7.581710815429688e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 4.76837158203125e-06s
INFO | --- Analysis for renewable_energy_generators took 11.184223890304565s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.08910703659057617s
Availability | VoID file availability check for research.data.gov.uk took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.269406795501709s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.679794311523438e-05s
Believability | Calculation of trust value for research.data.gov.uk took 4.291534423828125e-06s
INFO | --- Analysis for research-data-gov-uk took 3.0498440265655518s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 6.818771362304688e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2602510452270508s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.021144866943359375s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.24249267578125e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 6.9141387939453125e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.9489433765411377s
Availability | SPARQL endpoint availability check for Restaurantes took 4.172325134277344e-05s
Availability | VoID file availability check for Restaurantes took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2608668804168701s
Reputation | Calculation of the PageRank for Restaurantes took 0.021170377731323242s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.1948089599609375e-05s
Believability | Calculation of trust value for Restaurantes took 6.4373016357421875e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.9219658374786377s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.38690185546875e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2653322219848633s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02081894874572754s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.937980651855469e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 6.4373016357421875e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 3.5367815494537354s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.05651259422302246s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.737999439239502s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.266334533691406e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 7.62939453125e-06s
INFO | --- Analysis for revistas_turismo took 2.9216959476470947s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.27132153511047363s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2611274719238281s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011730194091796875s
Believability | Calculation of trust value for Revyu.com - Review Anything took 8.821487426757812e-06s
INFO | --- Analysis for revyu took 2.705371618270874s
Availability | SPARQL endpoint availability check for sdafsadf took 0.345322847366333s
Availability | VoID file availability check for sdafsadf took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.25932741165161133s
Reputation | Calculation of the PageRank for sdafsadf took 0.02084493637084961s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 3.838539123535156e-05s
Believability | Calculation of trust value for sdafsadf took 1.2636184692382812e-05s
INFO | --- Analysis for rgsdfg took 3.165144681930542s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.3392181396484375e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.26677775382995605s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.02120685577392578s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.221366882324219e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 8.106231689453125e-06s
INFO | --- Analysis for riese took 2.5405757427215576s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.100799560546875e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.2724442481994629s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020990848541259766s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 7.152557373046875e-06s
INFO | --- Analysis for rijksmuseum took 2.9077162742614746s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.6395065784454346s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2682797908782959s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.02074456214904785s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.364418029785156e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 6.9141387939453125e-06s
INFO | --- Analysis for rism took 3.6294772624969482s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.1787116527557373s
Availability | VoID file availability check for RISM Authority data took 0.0011897087097167969s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.27532076835632324s
Reputation | Calculation of the PageRank for RISM Authority data took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.696846008300781e-05s
Believability | Calculation of trust value for RISM Authority data took 8.58306884765625e-06s
INFO | --- Analysis for rism-authorities took 3.17604398727417s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.601478576660156e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2722494602203369s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.198883056640625e-06s
INFO | --- Analysis for rk took 2.3945534229278564s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.04468107223510742s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.2571408748626709s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02809286117553711s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002353191375732422s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.550504446029663s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.04457521438598633s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2850065231323242s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00015926361083984375s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.607726812362671s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.05156898498535156s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2510228157043457s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020754575729370117s
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.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00020384788513183594s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.4573850631713867s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04553818702697754s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2906472682952881s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00016307830810546875s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.533700704574585s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.04310917854309082s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.24390816688537598s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00017690658569335938s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.481938362121582s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.04684090614318848s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.27290916442871094s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020653247833251953s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 5.507469177246094e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 4.76837158203125e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.5420589447021484s
Availability | SPARQL endpoint availability check for crm took 4.1484832763671875e-05s
Availability | VoID file availability check for crm took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for crm took 0.25161194801330566s
Reputation | Calculation of the PageRank for crm took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for crm took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for crm took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for crm took 3.24249267578125e-05s
Believability | Calculation of trust value for crm took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.9386234283447266s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.03947043418884277s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.286313533782959s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.021024465560913086s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.000125885009765625s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.5390217304229736s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.052713871002197266s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.25365328788757324s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.2928924560546875e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.6176486015319824s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04940295219421387s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.24954986572265625s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002429485321044922s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.5349745750427246s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.04765820503234863s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.26347923278808594s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02060556411743164s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.534027099609375e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.5046255588531494s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.06709098815917969s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.26267385482788086s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.02098560333251953s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.608268737792969e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.4905691146850586s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.05194735527038574s
Availability | VoID file availability check for digitaleconomy took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.24695873260498047s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.0994415283203125e-05s
Believability | Calculation of trust value for digitaleconomy took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.520937204360962s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.04648017883300781s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2641589641571045s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014591217041015625s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.522597551345825s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.037656307220458984s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2552199363708496s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.173683166503906e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.950587749481201s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.410743713378906e-05s
Availability | VoID file availability check for enaktingpsi took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.26018524169921875s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.314018249511719e-05s
Believability | Calculation of trust value for enaktingpsi took 1.3828277587890625e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.912276268005371s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.048807382583618164s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.26757025718688965s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0001842975616455078s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-eprints took 2.4706525802612305s
Availability | SPARQL endpoint availability check for epsrc took 0.0436253547668457s
Availability | VoID file availability check for epsrc took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for epsrc took 0.24187111854553223s
Reputation | Calculation of the PageRank for epsrc took 0.020361661911010742s
Interlinking | Calculation of Degree of Connection for epsrc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.888938903808594e-05s
Believability | Calculation of trust value for epsrc took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.448906183242798s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.03792285919189453s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.27411723136901855s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.799003601074219e-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.52410888671875s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.05004453659057617s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2712881565093994s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.0001068115234375s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.659604072570801s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.076957702636719e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.2777729034423828s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.02080535888671875s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.3855438232421875e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-foreign took 3.0254647731781006s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.05189180374145508s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.25934386253356934s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 9.250640869140625e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.523414134979248s
Availability | SPARQL endpoint availability check for fun took 0.04391813278198242s
Availability | VoID file availability check for fun took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for fun took 0.27154016494750977s
Reputation | Calculation of the PageRank for fun took 0.02050471305847168s
Interlinking | Calculation of Degree of Connection for fun took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for fun took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for fun took 7.557868957519531e-05s
Believability | Calculation of trust value for fun took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.4565370082855225s
Availability | SPARQL endpoint availability check for gdlc took 0.047789812088012695s
Availability | VoID file availability check for gdlc took 0.0004286766052246094s
Completeness | Calculation of interlinking completeness for gdlc took 0.2734034061431885s
Reputation | Calculation of the PageRank for gdlc took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.890296936035156e-05s
Believability | Calculation of trust value for gdlc took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.486680030822754s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.04843640327453613s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2524878978729248s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.02061176300048828s
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.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011515617370605469s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-ibm took 2.5402543544769287s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.05176544189453125s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.2698478698730469s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00013875961303710938s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.6118743419647217s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.037400245666503906s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.27855992317199707s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00013899803161621094s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.625570297241211s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.05187702178955078s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.27997517585754395s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.200241088867188e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.5841057300567627s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.05129718780517578s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.27599644660949707s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.987022399902344e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.5067338943481445s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.04674339294433594s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2432558536529541s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020307302474975586s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007369518280029297s
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.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.472407341003418s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.05613827705383301s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2592134475708008s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.02031874656677246s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001621246337890625s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.492427349090576s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.05072379112243652s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.26167941093444824s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020833253860473633s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00014662742614746094s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.477675199508667s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.03899788856506348s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2584245204925537s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02144622802734375s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.271766662597656e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.5128161907196045s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.06902408599853516s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2758307456970215s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00015854835510253906s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.595548629760742s
Availability | SPARQL endpoint availability check for notube took 0.04517722129821777s
Availability | VoID file availability check for notube took 0.000339508056640625s
Completeness | Calculation of interlinking completeness for notube took 0.25502800941467285s
Reputation | Calculation of the PageRank for notube took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for notube took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for notube took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for notube took 4.315376281738281e-05s
Believability | Calculation of trust value for notube took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.5077786445617676s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.05271458625793457s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.25132322311401367s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020711898803710938s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.000141143798828125s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.465548276901245s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.052158355712890625s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2624828815460205s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.021165847778320312s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0001575946807861328s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.5716779232025146s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.4345855712890625e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.2510998249053955s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020795345306396484s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 3.1948089599609375e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.8820934295654297s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.04659008979797363s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0005102157592773438s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.27627992630004883s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.939338684082031e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for rkb-explorer-os took 2.557523488998413s
Availability | SPARQL endpoint availability check for photos took 0.03880929946899414s
Availability | VoID file availability check for photos took 0.0003826618194580078s
Completeness | Calculation of interlinking completeness for photos took 0.2637958526611328s
Reputation | Calculation of the PageRank for photos took 0.020919322967529297s
Interlinking | Calculation of Degree of Connection for photos took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for photos took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for photos took 7.510185241699219e-05s
Believability | Calculation of trust value for photos took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.4597129821777344s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.0377497673034668s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.27564382553100586s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00011301040649414062s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.538841485977173s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.03872323036193848s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2722198963165283s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.0002014636993408203s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.45737624168396s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.049364328384399414s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.2716054916381836s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001437664031982422s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.517103910446167s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.054494380950927734s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.27245330810546875s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.393692016601562e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 8.58306884765625e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.509596824645996s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0537567138671875s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.28255581855773926s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0001270771026611328s
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.5614445209503174s
Availability | SPARQL endpoint availability check for roni took 0.05067753791809082s
Availability | VoID file availability check for roni took 0.00036144256591796875s
Completeness | Calculation of interlinking completeness for roni took 0.2567729949951172s
Reputation | Calculation of the PageRank for roni took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for roni took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for roni took 3.147125244140625e-05s
Believability | Calculation of trust value for roni took 9.059906005859375e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.4617362022399902s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.043303728103637695s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004124641418457031s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.30388402938842773s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00022220611572265625s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.5521016120910645s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04999423027038574s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.29500913619995117s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00011277198791503906s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.5256896018981934s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.05223989486694336s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.25971531867980957s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010275840759277344s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.5159411430358887s
Availability | SPARQL endpoint availability check for webconf took 0.04913902282714844s
Availability | VoID file availability check for webconf took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for webconf took 0.26656413078308105s
Reputation | Calculation of the PageRank for webconf took 0.020750999450683594s
Interlinking | Calculation of Degree of Connection for webconf took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for webconf took 0.0001087188720703125s
Believability | Calculation of trust value for webconf took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-webconf took 12.863417863845825s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.04717230796813965s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.2584531307220459s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.581710815429688e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.4858546257019043s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.04283022880554199s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2715275287628174s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00021076202392578125s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.5078847408294678s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.06563997268676758s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2726743221282959s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02054595947265625s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.775161743164062e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.624180555343628s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.267692565917969e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2573082447052002s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0009119510650634766s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.886222839355469e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.867813110351562e-06s
INFO | --- Analysis for rkb_explorer_data took 2.868814706802368s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.4766380786895752s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0007331371307373047s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.24612712860107422s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 0.00019860267639160156s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 6.4373016357421875e-06s
INFO | --- Analysis for roceeh-road took 3.957709789276123s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.172325134277344e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.3324286937713623s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.170967102050781e-05s
Believability | Calculation of trust value for The Rosetta Project took 8.58306884765625e-06s
INFO | --- Analysis for rosetta-project took 3.010108470916748s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 5.435943603515625e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0008060932159423828s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.25206422805786133s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.170967102050781e-05s
Believability | Calculation of trust value for ontology terrorist attack took 7.152557373046875e-06s
INFO | --- Analysis for ROSHANI took 3.644035577774048s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.315376281738281e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.28726673126220703s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02086472511291504s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.504753112792969e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 7.3909759521484375e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.3847975730895996s
Availability | SPARQL endpoint availability check for x took 4.38690185546875e-05s
Availability | VoID file availability check for x took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for x took 0.2674109935760498s
Reputation | Calculation of the PageRank for x took 0.02068185806274414s
Interlinking | Calculation of Degree of Connection for x took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for x took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for x took 3.1948089599609375e-05s
Believability | Calculation of trust value for x took 6.198883056640625e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.3897385597229004s
Availability | SPARQL endpoint availability check for Rpm Find took 4.124641418457031e-05s
Availability | VoID file availability check for Rpm Find took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.2622356414794922s
Reputation | Calculation of the PageRank for Rpm Find took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.123283386230469e-05s
Believability | Calculation of trust value for Rpm Find took 7.62939453125e-06s
INFO | --- Analysis for rpm_find took 2.951930522918701s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.506111145019531e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.2559518814086914s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 7.486343383789062e-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.291935443878174s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 4.410743713378906e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.26692914962768555s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020972728729248047s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 7.677078247070312e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 7.3909759521484375e-06s
INFO | --- Analysis for rubentaelman took 2.846479892730713s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.363059997558594e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2843804359436035s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.02070903778076172s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.58306884765625e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.0728836059570312e-05s
INFO | --- Analysis for rubenverborgh took 3.7783730030059814s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 393.5491774082184s
Availability | VoID file availability check for Russian Universities Specialities took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.7296147346496582s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.76837158203125e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 7.62939453125e-06s
INFO | --- Analysis for russian-universities-specialities took 678.7635805606842s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.1961669921875e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.7045540809631348s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020792484283447266s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.0994415283203125e-05s
Believability | Calculation of trust value for RuThes Cloud took 7.152557373046875e-06s
INFO | --- Analysis for ruthes took 6.1854188442230225s
Availability | SPARQL endpoint availability check for RxNorm took 4.220008850097656e-05s
Availability | VoID file availability check for RxNorm took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2690737247467041s
Reputation | Calculation of the PageRank for RxNorm took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.361701965332031e-05s
Believability | Calculation of trust value for RxNorm took 1.621246337890625e-05s
INFO | --- Analysis for rxnorm took 3.790794610977173s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 3.2210402488708496s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.2724299430847168s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02023482322692871s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 2.86102294921875e-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.228850603103638s
Availability | SPARQL endpoint availability check for SALDO took 4.220008850097656e-05s
Availability | VoID file availability check for SALDO took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for SALDO took 0.7353625297546387s
Reputation | Calculation of the PageRank for SALDO took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for SALDO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for SALDO took 3.0994415283203125e-05s
Believability | Calculation of trust value for SALDO took 6.9141387939453125e-06s
INFO | --- Analysis for saldo took 3.8867766857147217s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.0594372749328613s
Availability | VoID file availability check for SALDO-RDF took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2540879249572754s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for SALDO-RDF took 7.62939453125e-06s
INFO | --- Analysis for saldo-rdf took 5.517660140991211s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.5963292121887207s
Availability | VoID file availability check for SALDOM-RDF took 0.0005977153778076172s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.27716565132141113s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0008947849273681641s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.719329833984375e-05s
Believability | Calculation of trust value for SALDOM-RDF took 6.198883056640625e-06s
INFO | --- Analysis for saldom-rdf took 4.729131460189819s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 5.435943603515625e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2890284061431885s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010704994201660156s
Believability | Calculation of trust value for Salzburgerland DE took 6.4373016357421875e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.096614360809326s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.315376281738281e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.26972007751464844s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00011086463928222656s
Believability | Calculation of trust value for Salzburgerland EN took 9.059906005859375e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.8785171508789062s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.482269287109375e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.28841137886047363s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.0001087188720703125s
Believability | Calculation of trust value for Salzburgerland IT took 8.821487426757812e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.8723814487457275s
Availability | SPARQL endpoint availability check for sameAs.org took 4.315376281738281e-05s
Availability | VoID file availability check for sameAs.org took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.25939202308654785s
Reputation | Calculation of the PageRank for sameAs.org took 0.020741701126098633s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.266334533691406e-05s
Believability | Calculation of trust value for sameAs.org took 8.821487426757812e-06s
INFO | --- Analysis for sameas-org took 2.9041907787323s
Availability | SPARQL endpoint availability check for sandrart.net took 4.458427429199219e-05s
Availability | VoID file availability check for sandrart.net took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.26221561431884766s
Reputation | Calculation of the PageRank for sandrart.net took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 7.891654968261719e-05s
Believability | Calculation of trust value for sandrart.net took 7.867813110351562e-06s
INFO | --- Analysis for sandrart-net took 4.375685214996338s
Availability | SPARQL endpoint availability check for Taxons  took 0.32674646377563477s
Availability | VoID file availability check for Taxons  took 0.0005304813385009766s
Extra | Recovery of all triples for Taxons  took 25.495700120925903s
Performance | Total latancy measurement for Taxons  took 0.43195033073425293s
Amount of data | Number of triples check for Taxons  took 2.197800636291504s
Interoperability | New terms check for Taxons  took 2.19899845123291s
Versatility | Languages check for Taxons  took 42.19199776649475s
Interpretability | Number of blank nodes check for Taxons  took 1.057086706161499s
Security | Check HTTPS for Taxons  took 0.1943988800048828s
Interpretability | RDF structures check for Taxons  took 1.3699889183044434s
Versatility | Serialization formats check for Taxons  took 0.6610357761383057s
Availability | RDF dump link check for Taxons  took 0.34111571311950684s
License | MR license check for Taxons  took 2.378406286239624s
License | HR license check for Taxons  took 2.3967950344085693s
Amount of data | Number of property check for Taxons  took 0.12220096588134766s
Understandability | Number of label check for Taxons  took 5.418377876281738s
Understandability | URI regex check for Taxons  took 1.2035892009735107s
Understandability | Vocabs check for Taxons  took 0.22752952575683594s
Verifiability | Authors check for Taxons  took 0.12172341346740723s
Verifiability | Publishers check for Taxons  took 0.08751273155212402s
Performance | Throughput check for Taxons  took 10.498432636260986s
Amount of data | Check the number of entities for Taxons  took 8.273124694824219e-05s
Verifiability | Contribs. check for Taxons  took 0.07599139213562012s
Interlinking | sameAs chians check for Taxons  took 0.14075279235839844s
Interlinking | skos check for Taxons  took 0.17907285690307617s
Interlinking | skos check for Taxons  took 0.095458984375s
Timeliness | dataset update frequency check for Taxons  took 0.5077366828918457s
Currency | Creation date check for Taxons  took 0.2000727653503418s
Currency | Modification date check for Taxons  took 0.24095749855041504s
Rep.Conc. | URIs length for Taxons  took 10.965663194656372s
Interoperability | New vocabularies check for Taxons  took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.1133267879486084s
Accuracy | Check Functional Property for Taxons  took 0.5308537483215332s
Accuracy | Check Inverse Functional Property for Taxons  took 0.47835397720336914s
Accuracy | Check Empty annotation labels for Taxons  took 5.491657495498657s
Accuracy | Check White space in annotation for Taxons  took 0.31824803352355957s
Accuracy | Check Datatype consistency for Taxons  took 0.2704033851623535s
Consistency | Disjoint class check for Taxons  took 0.12674808502197266s
Consistency | Check Misplaced properties for Taxons  took 4.289301872253418s
Consistency | Misplaced classes for Taxons  took 0.9826376438140869s
Consistency | Check Ontology hijacking for Taxons  took 5.029856204986572s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.1585443019866943s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.441193342208862s
Conciseness | Check Extensional conciseness for Taxons  took 0.28371143341064453s
Conciseness | Check Intensional conciseness for Taxons  took 0.1859574317932129s
Security | Sign check for Taxons  took 1.1880066394805908s
Availability | Check URIs Dereferenciability for Taxons  took 1720.1623017787933s
Completeness | Calculation of interlinking completeness for Taxons  took 1.606689214706421s
Reputation | Calculation of the PageRank for Taxons  took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.296966552734375e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 1.9073486328125e-06s
Believability | Calculation of trust value for Taxons  took 7.867813110351562e-06s
INFO | --- Analysis for sandre took 1925.5054140090942s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 2.1756112575531006s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.7096686363220215s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.337860107421875e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for sanskrit-english-lexicon took 11.58160948753357s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 265.0051951408386s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.3189845085144043s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.719329833984375e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for santillana_guide_dataset took 671.7065737247467s
Availability | SPARQL endpoint availability check for SATAR test  took 4.3392181396484375e-05s
Availability | VoID file availability check for SATAR test  took 0.0003478527069091797s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.2615485191345215s
Reputation | Calculation of the PageRank for SATAR test  took 0.020842552185058594s
Interlinking | Calculation of Degree of Connection for SATAR test  took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 8.535385131835938e-05s
Believability | Calculation of trust value for SATAR test  took 7.62939453125e-06s
INFO | --- Analysis for SATAR_test took 4.709860801696777s
Availability | SPARQL endpoint availability check for SCBG Data took 21.533985137939453s
Availability | VoID file availability check for SCBG Data took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.7452912330627441s
Reputation | Calculation of the PageRank for SCBG Data took 0.02014470100402832s
Interlinking | Calculation of Degree of Connection for SCBG Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.058547973632812e-05s
Believability | Calculation of trust value for SCBG Data took 7.3909759521484375e-06s
INFO | --- Analysis for SCBG-Data took 56.352885484695435s
Availability | SPARQL endpoint availability check for schema.org took 5.0067901611328125e-05s
Availability | VoID file availability check for schema.org took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for schema.org took 0.26000165939331055s
Reputation | Calculation of the PageRank for schema.org took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for schema.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.504753112792969e-05s
Believability | Calculation of trust value for schema.org took 6.9141387939453125e-06s
INFO | --- Analysis for schema-org took 3.7882089614868164s
Availability | SPARQL endpoint availability check for Schemantra took 4.458427429199219e-05s
Availability | VoID file availability check for Schemantra took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2560718059539795s
Reputation | Calculation of the PageRank for Schemantra took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for Schemantra took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Schemantra took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.170967102050781e-05s
Believability | Calculation of trust value for Schemantra took 6.9141387939453125e-06s
INFO | --- Analysis for Schemantra took 2.790548801422119s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.380763053894043s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0006558895111083984s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.2760624885559082s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.314018249511719e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 6.4373016357421875e-06s
INFO | --- Analysis for schemapedia took 33.6227822303772s
Availability | SPARQL endpoint availability check for scholarlydata took 4.172325134277344e-05s
Availability | VoID file availability check for scholarlydata took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.2861313819885254s
Reputation | Calculation of the PageRank for scholarlydata took 0.02057480812072754s
Interlinking | Calculation of Degree of Connection for scholarlydata took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 3.0279159545898438e-05s
Believability | Calculation of trust value for scholarlydata took 8.106231689453125e-06s
INFO | --- Analysis for scholarlydata took 2.9718921184539795s
Availability | SPARQL endpoint availability check for Scholarometer took 4.291534423828125e-05s
Availability | VoID file availability check for Scholarometer took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2652552127838135s
Reputation | Calculation of the PageRank for Scholarometer took 0.0204164981842041s
Interlinking | Calculation of Degree of Connection for Scholarometer took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.940696716308594e-05s
Believability | Calculation of trust value for Scholarometer took 6.67572021484375e-06s
INFO | --- Analysis for scholarometer took 7.8052756786346436s
Availability | SPARQL endpoint availability check for Science Commons took 7.843971252441406e-05s
Availability | VoID file availability check for Science Commons took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Science Commons took 0.26952242851257324s
Reputation | Calculation of the PageRank for Science Commons took 0.020479202270507812s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.9802322387695312e-05s
Believability | Calculation of trust value for Science Commons took 7.867813110351562e-06s
INFO | --- Analysis for science_commons took 3.369797706604004s
Availability | SPARQL endpoint availability check for ScienceWise took 4.100799560546875e-05s
Availability | VoID file availability check for ScienceWise took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2672085762023926s
Reputation | Calculation of the PageRank for ScienceWise took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for ScienceWise took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007822513580322266s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 2.9325485229492188e-05s
Believability | Calculation of trust value for ScienceWise took 6.9141387939453125e-06s
INFO | --- Analysis for sciencewise took 2.9780774116516113s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.3392181396484375e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2959132194519043s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.9325485229492188e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 7.3909759521484375e-06s
INFO | --- Analysis for scoreboard took 4.529948949813843s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.363059997558594e-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.0006284713745117188s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.7058045864105225s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020315170288085938s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.956390380859375e-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 16.725130558013916s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.267692565917969e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006082057952880859s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.25864696502685547s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020255327224731445s
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.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.2901763916015625e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.152557373046875e-06s
INFO | --- Analysis for SDG took 3.564565896987915s
Availability | SPARQL endpoint availability check for sears.com took 4.2438507080078125e-05s
Availability | VoID file availability check for sears.com took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for sears.com took 0.27045607566833496s
Reputation | Calculation of the PageRank for sears.com took 0.02033066749572754s
Interlinking | Calculation of Degree of Connection for sears.com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for sears.com took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for sears.com took 7.319450378417969e-05s
Believability | Calculation of trust value for sears.com took 6.67572021484375e-06s
INFO | --- Analysis for sears took 4.127837896347046s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.061982154846191406s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.27383875846862793s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020392417907714844s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.320808410644531e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.291534423828125e-06s
INFO | --- Analysis for sec-rdfabout took 6.058889865875244s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.61869764328003s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0007162094116210938s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.26897549629211426s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020379066467285156s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.296966552734375e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for secold took 168.28523778915405s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.553794860839844e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.2673807144165039s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 3.0040740966796875e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 7.3909759521484375e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 3.9602670669555664s
Availability | SPARQL endpoint availability check for semanlink took 4.3392181396484375e-05s
Availability | VoID file availability check for semanlink took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for semanlink took 0.27079296112060547s
Reputation | Calculation of the PageRank for semanlink took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014853477478027344s
Believability | Calculation of trust value for semanlink took 6.9141387939453125e-06s
INFO | --- Analysis for semanlink took 3.763181686401367s
Availability | SPARQL endpoint availability check for Semantic Library took 4.172325134277344e-05s
Availability | VoID file availability check for Semantic Library took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2577707767486572s
Reputation | Calculation of the PageRank for Semantic Library took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for Semantic Library took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.8133392333984375e-05s
Believability | Calculation of trust value for Semantic Library took 7.867813110351562e-06s
INFO | --- Analysis for semantic-library took 2.985635280609131s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.25017714500427246s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.075599670410156e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.867813110351562e-06s
INFO | --- Analysis for semantic-profiling-network took 3.012542486190796s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.06696295738220215s
Availability | VoID file availability check for Semantic Universe Data took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.24984407424926758s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.695487976074219e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.62939453125e-06s
INFO | --- Analysis for semantic-universe took 2.5300869941711426s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.307318210601807s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0008578300476074219s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.28116440773010254s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.021143674850463867s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00012969970703125s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for semantic-web-dog-food took 83.24779939651489s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 8.320808410644531e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2641592025756836s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007994174957275391s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 5.030632019042969e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.495819330215454s
Availability | SPARQL endpoint availability check for semantic-web-journal took 6.747245788574219e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2824513912200928s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.0994415283203125e-05s
Believability | Calculation of trust value for semantic-web-journal took 7.867813110351562e-06s
INFO | --- Analysis for semantic-web-journal took 2.9120397567749023s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.291534423828125e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.28658533096313477s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020541906356811523s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.416175842285156e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 9.298324584960938e-06s
INFO | --- Analysis for semantic-xbrl took 3.471628427505493s
Availability | SPARQL endpoint availability check for Semantic Bible took 7.104873657226562e-05s
Availability | VoID file availability check for Semantic Bible took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.27890515327453613s
Reputation | Calculation of the PageRank for Semantic Bible took 0.02125072479248047s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0008463859558105469s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.62396240234375e-05s
Believability | Calculation of trust value for Semantic Bible took 8.106231689453125e-06s
INFO | --- Analysis for semantic_bible took 2.9320149421691895s
Availability | SPARQL endpoint availability check for SemanticQuran took 0.3314051628112793s
Availability | VoID file availability check for SemanticQuran took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.27239108085632324s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.43865966796875e-05s
Believability | Calculation of trust value for SemanticQuran took 7.62939453125e-06s
INFO | --- Analysis for semanticquran took 2.987307071685791s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.315376281738281e-05s
Availability | VoID file availability check for SemanticTweet took 0.0003962516784667969s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.26588010787963867s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.841255187988281e-05s
Believability | Calculation of trust value for SemanticTweet took 7.152557373046875e-06s
INFO | --- Analysis for semantictweet took 4.3893208503723145s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.220008850097656e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006620883941650391s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.2741990089416504s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02191448211669922s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0008800029754638672s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 9.322166442871094e-05s
Believability | Calculation of trust value for semanticweb.org took 7.867813110351562e-06s
INFO | --- Analysis for semanticweb-org took 22.817208766937256s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.07869386672973633s
Availability | VoID file availability check for Semantic CrunchBase took 0.0003833770751953125s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2867250442504883s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.985664367675781e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 6.9141387939453125e-06s
INFO | --- Analysis for semsol-crunchbase took 2.555187940597534s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.124641418457031e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.26387500762939453s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020827770233154297s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.266334533691406e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 7.3909759521484375e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.967617988586426s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.2703826427459717s
Availability | VoID file availability check for SentimentWortschatz took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.258500337600708s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.3392181396484375e-05s
Believability | Calculation of trust value for SentimentWortschatz took 7.3909759521484375e-06s
INFO | --- Analysis for sentiws took 3.302523374557495s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.016995906829834s
Availability | VoID file availability check for seoul-bike-data took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.26047444343566895s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 4.0531158447265625e-05s
Believability | Calculation of trust value for seoul-bike-data took 6.67572021484375e-06s
INFO | --- Analysis for seoul-bike-data took 72.50632572174072s
Availability | SPARQL endpoint availability check for Serendipity took 10.743256092071533s
Availability | VoID file availability check for Serendipity took 0.0003046989440917969s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2525949478149414s
Reputation | Calculation of the PageRank for Serendipity took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Serendipity took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Serendipity took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Serendipity took 7.05718994140625e-05s
Believability | Calculation of trust value for Serendipity took 7.152557373046875e-06s
INFO | --- Analysis for serendipity took 21.939526796340942s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.315376281738281e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.26148080825805664s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.9087066650390625e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 6.4373016357421875e-06s
INFO | --- Analysis for Sherry_Wine took 2.5815258026123047s
Availability | SPARQL endpoint availability check for Sherry Wine took 6.151199340820312e-05s
Availability | VoID file availability check for Sherry Wine took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.2662386894226074s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.0994415283203125e-05s
Believability | Calculation of trust value for Sherry Wine took 7.867813110351562e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.3851161003112793s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.22846126556396484s
Availability | VoID file availability check for Shoah victims? names took 0.0005631446838378906s
Extra | Recovery of all triples for Shoah victims? names took 1.6848039627075195s
Performance | Total latancy measurement for Shoah victims? names took 0.7188723087310791s
Amount of data | Number of triples check for Shoah victims? names took 1.4717113971710205s
Interoperability | New terms check for Shoah victims? names took 1.6318926811218262s
Versatility | Languages check for Shoah victims? names took 6.239465236663818s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.183497190475464s
Security | Check HTTPS for Shoah victims? names took 0.7085230350494385s
Interpretability | RDF structures check for Shoah victims? names took 0.15679192543029785s
Versatility | Serialization formats check for Shoah victims? names took 0.28911328315734863s
Availability | RDF dump link check for Shoah victims? names took 0.26175689697265625s
License | MR license check for Shoah victims? names took 0.32079505920410156s
License | HR license check for Shoah victims? names took 8.614494800567627s
Amount of data | Number of property check for Shoah victims? names took 0.3095870018005371s
Understandability | Number of label check for Shoah victims? names took 0.9773194789886475s
Understandability | URI regex check for Shoah victims? names took 0.5463438034057617s
Understandability | Vocabs check for Shoah victims? names took 0.1962583065032959s
Verifiability | Authors check for Shoah victims? names took 0.153336763381958s
Verifiability | Publishers check for Shoah victims? names took 0.11389541625976562s
Performance | Throughput check for Shoah victims? names took 10.638413906097412s
Amount of data | Check the number of entities for Shoah victims? names took 8.606910705566406e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.27396655082702637s
Interlinking | sameAs chians check for Shoah victims? names took 0.21698713302612305s
Interlinking | skos check for Shoah victims? names took 0.22390174865722656s
Interlinking | skos check for Shoah victims? names took 0.0723419189453125s
Timeliness | dataset update frequency check for Shoah victims? names took 0.2600862979888916s
Currency | Creation date check for Shoah victims? names took 0.45938730239868164s
Currency | Modification date check for Shoah victims? names took 0.18778777122497559s
Rep.Conc. | URIs length for Shoah victims? names took 2.9539153575897217s
Interoperability | New vocabularies check for Shoah victims? names took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.09434843063354492s
Accuracy | Check Functional Property for Shoah victims? names took 0.16631603240966797s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.16144132614135742s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.538137674331665s
Accuracy | Check White space in annotation for Shoah victims? names took 0.028873443603515625s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.028272628784179688s
Consistency | Disjoint class check for Shoah victims? names took 0.2918868064880371s
Consistency | Check Misplaced properties for Shoah victims? names took 2.0782744884490967s
Consistency | Misplaced classes for Shoah victims? names took 0.257244348526001s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.5298912525177002s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.1324877738952637s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.013960361480713s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.029917001724243164s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.2853519916534424s
Security | Sign check for Shoah victims? names took 0.5068175792694092s
Availability | Check URIs Dereferenciability for Shoah victims? names took 2566.9622411727905s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.7073991298675537s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007848739624023438s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 6.651878356933594e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.6689300537109375e-06s
Believability | Calculation of trust value for Shoah victims? names took 6.67572021484375e-06s
INFO | --- Analysis for shoah-victims-names took 2672.098047018051s
Availability | SPARQL endpoint availability check for Person took 4.3392181396484375e-05s
Availability | VoID file availability check for Person took 0.0003361701965332031s
Completeness | Calculation of interlinking completeness for Person took 0.2587928771972656s
Reputation | Calculation of the PageRank for Person took 0.020133256912231445s
Interlinking | Calculation of Degree of Connection for Person took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Person took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Person took 2.7894973754882812e-05s
Believability | Calculation of trust value for Person took 1.7404556274414062e-05s
INFO | --- Analysis for Shripriya_Dubey took 3.358596086502075s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.267692565917969e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.25053954124450684s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.7179718017578125e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 7.3909759521484375e-06s
INFO | --- Analysis for Shutterstock took 2.8122599124908447s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.124641418457031e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2778201103210449s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.0279159545898438e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 6.67572021484375e-06s
INFO | --- Analysis for simile_data_collection took 4.478294134140015s
Availability | SPARQL endpoint availability check for SIMPLE took 4.4345855712890625e-05s
Availability | VoID file availability check for SIMPLE took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.27004361152648926s
Reputation | Calculation of the PageRank for SIMPLE took 0.020387649536132812s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 3.910064697265625e-05s
Believability | Calculation of trust value for SIMPLE took 8.344650268554688e-06s
INFO | --- Analysis for simple took 9.385048151016235s
Availability | SPARQL endpoint availability check for SITC-V4 took 29.744311332702637s
Availability | VoID file availability check for SITC-V4 took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.723487377166748s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020852088928222656s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.4345855712890625e-05s
Believability | Calculation of trust value for SITC-V4 took 4.5299530029296875e-06s
INFO | --- Analysis for sitc-v4 took 142.28351950645447s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 6.961822509765625e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.26975226402282715s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.315376281738281e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 6.67572021484375e-06s
INFO | --- Analysis for sli_galnet_rdf took 12.94691801071167s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.291534423828125e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.27056074142456055s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 2.9325485229492188e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 7.3909759521484375e-06s
INFO | --- Analysis for slideshare2rdf took 2.4367949962615967s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 5.412101745605469e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.25235605239868164s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.021016836166381836s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 7.152557373046875e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.8678605556488037s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.7848358154296875s
Availability | VoID file availability check for Linked Stage Graph took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.26131582260131836s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 4.9591064453125e-05s
Believability | Calculation of trust value for Linked Stage Graph took 6.9141387939453125e-06s
INFO | --- Analysis for slod took 3.8147547245025635s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.2438507080078125e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.2658421993255615s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.147125244140625e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.3909759521484375e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.9237396717071533s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 393.4885063171387s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.7118403911590576s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 9.989738464355469e-05s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Smart_POI_dataset took 668.43394947052s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 6.644535064697266s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.6844677925109863s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.02089667320251465s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 5.841255187988281e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 7.62939453125e-06s
INFO | --- Analysis for smartlink took 15.162930250167847s
Availability | SPARQL endpoint availability check for SNIK took 0.4216938018798828s
Availability | VoID file availability check for SNIK took 0.0007874965667724609s
Extra | Recovery of all triples for SNIK took 7.239848613739014s
Performance | Total latancy measurement for SNIK took 0.9899420738220215s
Amount of data | Number of triples check for SNIK took 0.18468713760375977s
Interoperability | New terms check for SNIK took 1.368680477142334s
Versatility | Languages check for SNIK took 0.23086762428283691s
Interpretability | Number of blank nodes check for SNIK took 0.18570661544799805s
Interpretability | RDF structures check for SNIK took 0.19753026962280273s
Versatility | Serialization formats check for SNIK took 0.19678616523742676s
Availability | RDF dump link check for SNIK took 0.19536495208740234s
License | MR license check for SNIK took 0.19630146026611328s
License | HR license check for SNIK took 0.23405766487121582s
Amount of data | Number of property check for SNIK took 0.18565845489501953s
Understandability | Number of label check for SNIK took 0.20035099983215332s
Understandability | URI regex check for SNIK took 0.40549230575561523s
Understandability | Vocabs check for SNIK took 0.19617509841918945s
Verifiability | Authors check for SNIK took 0.18474411964416504s
Verifiability | Publishers check for SNIK took 0.1949315071105957s
Performance | Throughput check for SNIK took 11.404600381851196s
Amount of data | Check the number of entities for SNIK took 7.05718994140625e-05s
Verifiability | Contribs. check for SNIK took 0.20218157768249512s
Interlinking | sameAs chians check for SNIK took 0.19631052017211914s
Interlinking | skos check for SNIK took 0.19729924201965332s
Interlinking | skos check for SNIK took 0.18467307090759277s
Timeliness | dataset update frequency check for SNIK took 0.20753049850463867s
Currency | Creation date check for SNIK took 0.38042330741882324s
Currency | Modification date check for SNIK took 0.40306663513183594s
Rep.Conc. | URIs length for SNIK took 2.0040767192840576s
Interoperability | New vocabularies check for SNIK took 5.7220458984375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.19472575187683105s
Accuracy | Check Functional Property for SNIK took 0.20699238777160645s
Accuracy | Check Inverse Functional Property for SNIK took 0.19418787956237793s
Accuracy | Check Empty annotation labels for SNIK took 0.7800958156585693s
Accuracy | Check White space in annotation for SNIK took 0.0274660587310791s
Accuracy | Check Datatype consistency for SNIK took 0.22089338302612305s
Consistency | Disjoint class check for SNIK took 0.19423842430114746s
Consistency | Check Misplaced properties for SNIK took 0.6629762649536133s
Consistency | Misplaced classes for SNIK took 0.6803042888641357s
Consistency | Check Ontology hijacking for SNIK took 1.763976812362671s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.1596450805664062s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.4401271343231201s
Conciseness | Check Extensional conciseness for SNIK took 0.1540687084197998s
Conciseness | Check Intensional conciseness for SNIK took 0.3055145740509033s
Security | Sign check for SNIK took 0.1856675148010254s
Availability | Check URIs Dereferenciability for SNIK took 774.9006791114807s
Completeness | Calculation of interlinking completeness for SNIK took 0.9524345397949219s
Reputation | Calculation of the PageRank for SNIK took 0.020994901657104492s
Interlinking | Calculation of Degree of Connection for SNIK took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for SNIK took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.6689300537109375e-06s
Believability | Calculation of trust value for SNIK took 7.62939453125e-06s
INFO | --- Analysis for snik took 835.2233724594116s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.363059997558594e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.7572052478790283s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.0209805965423584s
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.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.123283386230469e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 1.1682510375976562e-05s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 5.383835554122925s
Availability | SPARQL endpoint availability check for SocialLink took 1.4660160541534424s
Availability | VoID file availability check for SocialLink took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for SocialLink took 0.28655076026916504s
Reputation | Calculation of the PageRank for SocialLink took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.390975952148438e-05s
Believability | Calculation of trust value for SocialLink took 6.67572021484375e-06s
INFO | --- Analysis for SocialLink took 5.915003061294556s
Availability | SPARQL endpoint availability check for SocialLink took 4.4345855712890625e-05s
Availability | VoID file availability check for SocialLink took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for SocialLink took 0.24239158630371094s
Reputation | Calculation of the PageRank for SocialLink took 0.020739078521728516s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.266334533691406e-05s
Believability | Calculation of trust value for SocialLink took 6.9141387939453125e-06s
INFO | --- Analysis for sociallink took 3.8321962356567383s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 6.580352783203125e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006215572357177734s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.2743527889251709s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.020663738250732422s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007703304290771484s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.2901763916015625e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 7.152557373046875e-06s
INFO | --- Analysis for SocialRoles took 12.22508978843689s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.27271223068237305s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0006265640258789062s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 23.61900019645691s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.5140848159790039s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.2473151683807373s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.3731153011322021s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.3686392307281494s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.20382118225097656s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.3630540370941162s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.11977338790893555s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.12342953681945801s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.8047363758087158s
License | MR license check for Social Semantic Web Thesaurus took 0.11207962036132812s
License | HR license check for Social Semantic Web Thesaurus took 0.1306591033935547s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.13609838485717773s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.12579917907714844s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.1932985782623291s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.13064169883728027s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.12842893600463867s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.11110305786132812s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.670352458953857s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 8.034706115722656e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.10237789154052734s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.12780094146728516s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.10722827911376953s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.09118413925170898s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.10583257675170898s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.17891645431518555s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.22650861740112305s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 2.2207298278808594s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.11141633987426758s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.10549807548522949s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.10130763053894043s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.5275413990020752s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012287616729736328s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.09259819984436035s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.2993025779724121s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.09559059143066406s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.2704362869262695s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.47752046585083s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.00016188621520996094s
Security | Sign check for Social Semantic Web Thesaurus took 0.08058929443359375s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 114.3441207408905s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.3824450969696045s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020514726638793945s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 0.00010776519775390625s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 243.06116437911987s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 392.1366488933563s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.710094690322876s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.020720720291137695s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.6716461181640625e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Soil_maps took 669.1903779506683s
Availability | SPARQL endpoint availability check for terrorrist ontology took 8.535385131835938e-05s
Availability | VoID file availability check for terrorrist ontology took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.7189438343048096s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.552436828613281e-05s
Believability | Calculation of trust value for terrorrist ontology took 7.3909759521484375e-06s
INFO | --- Analysis for somya_omer took 5.052597999572754s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.291534423828125e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005660057067871094s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.26833605766296387s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.2636184692382812e-05s
Believability | Calculation of trust value for Sonclubcx took 1.5735626220703125e-05s
INFO | --- Analysis for sonclubcx took 4.7583088874816895s
Availability | SPARQL endpoint availability check for SORS took 6.151199340820312e-05s
Availability | VoID file availability check for SORS took 0.0007376670837402344s
Completeness | Calculation of interlinking completeness for SORS took 0.2562980651855469s
Reputation | Calculation of the PageRank for SORS took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for SORS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SORS took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for SORS took 4.9114227294921875e-05s
Believability | Calculation of trust value for SORS took 4.76837158203125e-06s
INFO | --- Analysis for sors took 13.144390344619751s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.38690185546875e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.2534828186035156s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.024016141891479492s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0009360313415527344s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 4.0531158447265625e-05s
Believability | Calculation of trust value for Soudy České republiky took 8.58306884765625e-06s
INFO | --- Analysis for soudy--esk--republiky took 2.9294443130493164s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.3392181396484375e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.24126648902893066s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.1552734375e-05s
Believability | Calculation of trust value for southampton-ac-uk took 7.867813110351562e-06s
INFO | --- Analysis for southampton-ac-uk took 4.54743504524231s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.325906991958618s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.00057220458984375s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.2738642692565918s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.266334533691406e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 6.9141387939453125e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.701455354690552s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.4345855712890625e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0006139278411865234s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.3002440929412842s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020529747009277344s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.584426879882812e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.1682510375976562e-05s
INFO | --- Analysis for southampton-ecs-eprints took 4.366194725036621s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 20.455041646957397s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.2602224349975586s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.218650817871094e-05s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 6.67572021484375e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 53.09477496147156s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.09498310089111328s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2830164432525635s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.5299530029296875e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 5.9604644775390625e-06s
INFO | --- Analysis for sparql-endpoint-status took 3.379312515258789s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.2438507080078125e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.28824377059936523s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.6464462280273438e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 6.4373016357421875e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 3.0430684089660645s
Availability | SPARQL endpoint availability check for SPQR took 6.031990051269531e-05s
Availability | VoID file availability check for SPQR took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for SPQR took 0.26178932189941406s
Reputation | Calculation of the PageRank for SPQR took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for SPQR took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SPQR took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.9802322387695312e-05s
Believability | Calculation of trust value for SPQR took 6.9141387939453125e-06s
INFO | --- Analysis for spqr took 2.9119865894317627s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.1961669921875e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2847738265991211s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020674943923950195s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.559226989746094e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 7.3909759521484375e-06s
INFO | --- Analysis for springernaturescigraph took 3.0544490814208984s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.6253204345703125e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006067752838134766s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.26061177253723145s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 2.956390380859375e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 6.67572021484375e-06s
INFO | --- Analysis for srcmf took 12.92529845237732s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.6103639602661133s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.25972700119018555s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020496845245361328s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.673004150390625e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.0728836059570312e-05s
INFO | --- Analysis for ssf took 3.7620744705200195s
Availability | SPARQL endpoint availability check for SSF took 4.124641418457031e-05s
Availability | VoID file availability check for SSF took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for SSF took 0.7764601707458496s
Reputation | Calculation of the PageRank for SSF took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for SSF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SSF took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for SSF took 3.170967102050781e-05s
Believability | Calculation of trust value for SSF took 6.67572021484375e-06s
INFO | --- Analysis for ssf-lexicon took 3.4146430492401123s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 5.340576171875e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.2844846248626709s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.02094101905822754s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.7670135498046875e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 8.344650268554688e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.7391631603240967s
Availability | SPARQL endpoint availability check for STAC took 4.315376281738281e-05s
Availability | VoID file availability check for STAC took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for STAC took 0.2810385227203369s
Reputation | Calculation of the PageRank for STAC took 0.020573854446411133s
Interlinking | Calculation of Degree of Connection for STAC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for STAC took 2.9802322387695312e-05s
Believability | Calculation of trust value for STAC took 6.4373016357421875e-06s
INFO | --- Analysis for stac took 2.9690749645233154s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.1484832763671875e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.27109837532043457s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020449161529541016s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.552436828613281e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 5.7220458984375e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.958746910095215s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.38690185546875e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.28987622261047363s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0208127498626709s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.409385681152344e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.344650268554688e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.189772367477417s
Availability | SPARQL endpoint availability check for Stammbuch took 4.9591064453125e-05s
Availability | VoID file availability check for Stammbuch took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.2597668170928955s
Reputation | Calculation of the PageRank for Stammbuch took 0.020560264587402344s
Interlinking | Calculation of Degree of Connection for Stammbuch took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 3.123283386230469e-05s
Believability | Calculation of trust value for Stammbuch took 6.9141387939453125e-06s
INFO | --- Analysis for Stammbuch took 2.4211461544036865s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.5281991958618164s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2640666961669922s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 1.049041748046875e-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.00010585784912109375s
Believability | Calculation of trust value for statistics.data.gov.uk took 6.198883056640625e-06s
INFO | --- Analysis for statistics-data-gov-uk took 4.174938917160034s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.220008850097656e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.2583448886871338s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 3.1948089599609375e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 8.106231689453125e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.904235601425171s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0010874271392822266s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.2723660469055176s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.02022266387939453s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-1w6-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-1w6-org took 3.1443800926208496s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.26613831520080566s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.437301635742188e-05s
Believability | Calculation of trust value for statusnet-20100-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-20100-org took 2.3361501693725586s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0003249645233154297s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.24299931526184082s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 7.081031799316406e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.565697193145752s
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.0002295970916748047s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.2784421443939209s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007297992706298828s
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.419930934906006s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.29872918128967285s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.012222290039062e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.533806562423706s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.25273799896240234s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010657310485839844s
Believability | Calculation of trust value for statusnet-bka-li took 7.62939453125e-06s
INFO | --- Analysis for statusnet-bka-li took 2.6359570026397705s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.2611544132232666s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.886222839355469e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.4965362548828125s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.2601444721221924s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.023548126220703125s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.000978231430053711s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.6743621826171875e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.839312791824341s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.001102447509765625s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.26281023025512695s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 4.887580871582031e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.520667791366577s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0005881786346435547s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.27253222465515137s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.0001125335693359375s
Believability | Calculation of trust value for statusnet-chromic-org took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.5293266773223877s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0007464885711669922s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.26380395889282227s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 8.153915405273438e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 6.306934833526611s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.839897155761719e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.25043630599975586s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020554065704345703s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.507469177246094e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.412724494934082s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0006210803985595703s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2563486099243164s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.985664367675781e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.320230484008789s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.24332022666931152s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02033400535583496s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.584810972213745s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 6.937980651855469e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.000568389892578125s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.27458739280700684s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.4849853515625e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.4023818969726562s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.57763671875e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0006086826324462891s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2569921016693115s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.3459041118621826s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2837247848510742s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020786762237548828s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-dtdns-net took 22.358867645263672s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.26770520210266113s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020460128784179688s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.790855407714844e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.3810293674468994s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0006303787231445312s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.29857659339904785s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.02113175392150879s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.605552673339844e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.628070592880249s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0014765262603759766s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.2582123279571533s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020579814910888672s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 0.00010466575622558594s
Believability | Calculation of trust value for statusnet-fcac-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.350561380386353s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 7.104873657226562e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2562987804412842s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020467519760131836s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.507469177246094e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.0647106170654297s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0007016658782958984s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.2654273509979248s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.020478487014770508s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.00019097328186035156s
Believability | Calculation of trust value for statusnet-fragdev-com took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.2970805168151855s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.26922082901000977s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.653236389160156e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.3900938034057617s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 5.626678466796875e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.266573429107666s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010752677917480469s
Believability | Calculation of trust value for statusnet-gegeweb-org took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.5345840454101562s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.28049755096435547s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.985664367675781e-05s
Believability | Calculation of trust value for statusnet-glou-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-glou-org took 2.5875344276428223s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.28511905670166016s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012540817260742188s
Believability | Calculation of trust value for statusnet-gomertronic-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.3965885639190674s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 5.650520324707031e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2760155200958252s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-hackerposse-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.9393653869628906s
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.0005679130554199219s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.26399660110473633s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 5.054473876953125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.7089200019836426s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2550013065338135s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.083747863769531e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.377072334289551s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0006105899810791016s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.24939656257629395s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 3.396416425704956s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 5.91278076171875e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.27202463150024414s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.172325134277344e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.646498680114746s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 5.078315734863281e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0007231235504150391s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2599496841430664s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.507469177246094e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 7.62939453125e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.400676727294922s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.29916834831237793s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.0001201629638671875s
Believability | Calculation of trust value for statusnet-jonkman-ca took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.269615888595581s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 9.322166442871094e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2749347686767578s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020773649215698242s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 7.62939453125e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.5103774070739746s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 5.817413330078125e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.24795031547546387s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.3873982429504395s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2594480514526367s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 4.172325134277344e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2787787914276123s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.2528822422027588s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 6.985664367675781e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.347705125808716s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.24862170219421387s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020870685577392578s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.078315734863281e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.4482007026672363s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.26991963386535645s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.020444154739379883s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.5720884799957275s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.982948303222656e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.27210116386413574s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.5877442359924316s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.24592947959899902s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.0001125335693359375s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.415078639984131s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0006468296051025391s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.26575589179992676s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.02031540870666504s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.7676351070404053s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.26153016090393066s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.512901306152344e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.4223315715789795s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0003228187561035156s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2864084243774414s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.1975250244140625e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.4877240657806396s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 6.723403930664062e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2773580551147461s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014662742614746094s
Believability | Calculation of trust value for statusnet-macno-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-macno-org took 2.43821120262146s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.28887104988098145s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.4625608921051025s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006535053253173828s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.2819700241088867s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02092599868774414s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.940696716308594e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.216373443603516s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.2569704055786133s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015807151794433594s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-morphtown-de took 2.54343581199646s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.28572845458984375s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.00011110305786132812s
Believability | Calculation of trust value for statusnet-mrblog-nl took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.5415730476379395s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.25081515312194824s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.371811628341675s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.27830052375793457s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.023284912109375s
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.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.6743621826171875e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-my-status-tk took 2.45219087600708s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2685263156890869s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020686864852905273s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011086463928222656s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.3855526447296143s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.2590303421020508s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.604769468307495s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.28055405616760254s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02043008804321289s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 8.487701416015625e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.390206813812256s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0005929470062255859s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.25818490982055664s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.654594421386719e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.8241794109344482s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 5.817413330078125e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.27170562744140625s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.02065896987915039s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.887580871582031e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-panda-id-au took 3.416370391845703s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 5.5789947509765625e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.25020551681518555s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.942054748535156e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-piana-eu took 2.450737714767456s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0005173683166503906s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.28515005111694336s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.021366357803344727s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007236003875732422s
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.62939453125e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.523268461227417s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.249373197555542s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002276897430419922s
Believability | Calculation of trust value for statusnet-postblue-info took 7.62939453125e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.4186971187591553s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.27519774436950684s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.021624088287353516s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-progval-net took 2.4724624156951904s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 6.699562072753906e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.268810510635376s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020668745040893555s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011301040649414062s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.8616156578063965s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.26074886322021484s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2143361568450928s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2809901237487793s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00022101402282714844s
Believability | Calculation of trust value for statusnet-quitter-se took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-quitter-se took 3.7396860122680664s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0011336803436279297s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.28202056884765625s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.0001049041748046875s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.6766252517700195s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 5.745887756347656e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.259751558303833s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-recit-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-recit-org took 4.563472747802734s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 5.53131103515625e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.2738940715789795s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02048516273498535s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001552104949951172s
Believability | Calculation of trust value for statusnet-russwurm-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 3.342616081237793s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.76837158203125e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0005409717559814453s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.25954532623291016s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.02076411247253418s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.702278137207031e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-samnoble-org took 4.7928688526153564s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2984023094177246s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.02029132843017578s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.177757263183594e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.6387996673583984s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.2738974094390869s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02063727378845215s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.632110595703125e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.458547592163086s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.8160552978515625e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0008080005645751953s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2572669982910156s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 2.457775354385376s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 6.723403930664062e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0004220008850097656s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.27289319038391113s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.009506225585938e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.2861948013305664s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0007321834564208984s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2915530204772949s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021314620971679688s
Believability | Calculation of trust value for statusnet-skilledtests-com took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.9280033111572266s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2736635208129883s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010395050048828125s
Believability | Calculation of trust value for statusnet-somsants-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.4434573650360107s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.2504997253417969s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.000133514404296875s
Believability | Calculation of trust value for statusnet-soucy-cc took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-soucy-cc took 2.3729605674743652s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2746903896331787s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.028083324432373047s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0012600421905517578s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 9.036064147949219e-05s
Believability | Calculation of trust value for statusnet-spip-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-spip-org took 3.427029848098755s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.26126694679260254s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.437301635742188e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.4777705669403076s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.25190162658691406s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00011134147644042969s
Believability | Calculation of trust value for statusnet-ssweeny-net took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.328114032745361s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.2644832134246826s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.0002257823944091797s
Believability | Calculation of trust value for statusnet-status-net took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-status-net took 3.4470620155334473s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 8.96453857421875e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2737431526184082s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.463611364364624s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.000457763671875s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.26695728302001953s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.059906005859375e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.421694040298462s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.2822692394256592s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001239776611328125s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.5611660480499268s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0006046295166015625s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.308551549911499s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.271766662597656e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.006543397903442s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.27801966667175293s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010585784912109375s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.774167776107788s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0005891323089599609s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.25406646728515625s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.6716461181640625e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.4884021282196045s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0005731582641601562s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2760319709777832s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.0202791690826416s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.666937828063965s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0005822181701660156s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.288043737411499s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.886222839355469e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 3.347707748413086s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2589104175567627s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020702838897705078s
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.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for steak took 3.661369800567627s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 7.152557373046875e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2559623718261719s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.4836273193359375e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 7.152557373046875e-06s
INFO | --- Analysis for stitch-rameau took 4.023277759552002s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.6830894947052002s
Availability | VoID file availability check for Stone Tech Square took 0.0006170272827148438s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2884058952331543s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.3113021850585938e-05s
Believability | Calculation of trust value for Stone Tech Square took 7.867813110351562e-06s
INFO | --- Analysis for stone-tech-square-data took 4.980821132659912s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.267692565917969e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.25435471534729004s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 3.147125244140625e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 1.3113021850585938e-05s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.915144205093384s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 0.3784618377685547s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.00038623809814453125s
Extra | Recovery of all triples for STW Thesaurus for Economics took 40.20017075538635s
Performance | Total latancy measurement for STW Thesaurus for Economics took 1.117569923400879s
Amount of data | Number of triples check for STW Thesaurus for Economics took 0.6678581237792969s
Interoperability | New terms check for STW Thesaurus for Economics took 1.4197406768798828s
Versatility | Languages check for STW Thesaurus for Economics took 1.4786317348480225s
Interpretability | Number of blank nodes check for STW Thesaurus for Economics took 0.5030267238616943s
Security | Check HTTPS for STW Thesaurus for Economics took 0.15680885314941406s
Interpretability | RDF structures check for STW Thesaurus for Economics took 0.2683737277984619s
Versatility | Serialization formats check for STW Thesaurus for Economics took 0.22237491607666016s
Availability | RDF dump link check for STW Thesaurus for Economics took 0.225722074508667s
License | MR license check for STW Thesaurus for Economics took 0.21483302116394043s
License | HR license check for STW Thesaurus for Economics took 1.9793701171875s
Amount of data | Number of property check for STW Thesaurus for Economics took 0.25140905380249023s
Understandability | Number of label check for STW Thesaurus for Economics took 0.595750093460083s
Understandability | URI regex check for STW Thesaurus for Economics took 0.5028250217437744s
Understandability | Vocabs check for STW Thesaurus for Economics took 0.26460909843444824s
Verifiability | Authors check for STW Thesaurus for Economics took 0.2377314567565918s
Verifiability | Publishers check for STW Thesaurus for Economics took 0.24866485595703125s
Performance | Throughput check for STW Thesaurus for Economics took 10.667097568511963s
Amount of data | Check the number of entities for STW Thesaurus for Economics took 0.7820453643798828s
Verifiability | Contribs. check for STW Thesaurus for Economics took 0.2649059295654297s
Interlinking | sameAs chians check for STW Thesaurus for Economics took 0.2655160427093506s
Interlinking | skos check for STW Thesaurus for Economics took 0.345379114151001s
Interlinking | skos check for STW Thesaurus for Economics took 0.2861063480377197s
Timeliness | dataset update frequency check for STW Thesaurus for Economics took 0.25761866569519043s
Currency | Creation date check for STW Thesaurus for Economics took 0.4544360637664795s
Currency | Modification date check for STW Thesaurus for Economics took 0.47794485092163086s
Rep.Conc. | URIs length for STW Thesaurus for Economics took 10.550191879272461s
Consistency | Deprecated classes/propertiers check for STW Thesaurus for Economics took 0.25061774253845215s
Accuracy | Check Functional Property for STW Thesaurus for Economics took 0.23124217987060547s
Accuracy | Check Inverse Functional Property for STW Thesaurus for Economics took 0.261707067489624s
Accuracy | Check Empty annotation labels for STW Thesaurus for Economics took 10.4132559299469s
Accuracy | Check White space in annotation for STW Thesaurus for Economics took 1.0605947971343994s
Accuracy | Check Datatype consistency for STW Thesaurus for Economics took 2.4518072605133057s
Consistency | Disjoint class check for STW Thesaurus for Economics took 0.24842119216918945s
Consistency | Check Misplaced properties for STW Thesaurus for Economics took 1.3457129001617432s
Consistency | Check Ontology hijacking for STW Thesaurus for Economics took 2.361234188079834s
Consistency | Check Invalid usage of undefined classes for STW Thesaurus for Economics took 1.2398784160614014s
Consistency | Check Invalid usage of undefined properties for STW Thesaurus for Economics took 2.1502864360809326s
Conciseness | Check Extensional conciseness for STW Thesaurus for Economics took 1.6582469940185547s
Conciseness | Check Intensional conciseness for STW Thesaurus for Economics took 0.2709076404571533s
Security | Sign check for STW Thesaurus for Economics took 0.2534332275390625s
Availability | Check URIs Dereferenciability for STW Thesaurus for Economics took 2620.224710226059s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 1.5686595439910889s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.021350383758544922s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 3.3855438232421875e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00018024444580078125s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.3113021850585938e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 2763.5814225673676s
Availability | SPARQL endpoint availability check for SudershanTech took 4.38690185546875e-05s
Availability | VoID file availability check for SudershanTech took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.26364970207214355s
Reputation | Calculation of the PageRank for SudershanTech took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.147125244140625e-05s
Believability | Calculation of trust value for SudershanTech took 7.152557373046875e-06s
INFO | --- Analysis for SudershanTech took 4.635852575302124s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.9323379993438721s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2628037929534912s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.7206878662109375e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 7.152557373046875e-06s
INFO | --- Analysis for sudocfr took 9.11361837387085s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 308.5711188316345s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0008938312530517578s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.9177031517028809s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.02098226547241211s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 0.00010919570922851562s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 7.152557373046875e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 2225.235652446747s
Availability | SPARQL endpoint availability check for Surge Radio took 5.0067901611328125e-05s
Availability | VoID file availability check for Surge Radio took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.6996684074401855s
Reputation | Calculation of the PageRank for Surge Radio took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for Surge Radio took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 9.322166442871094e-05s
Believability | Calculation of trust value for Surge Radio took 7.152557373046875e-06s
INFO | --- Analysis for surge-radio took 6.758558988571167s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.363059997558594e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.26584649085998535s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.020738601684570312s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.0040740966796875e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 6.67572021484375e-06s
INFO | --- Analysis for SWAT took 24.76921844482422s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.267692565917969e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.42930006980895996s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2769961357116699s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.794929504394531e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 6.9141387939453125e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 5.64889121055603s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.0655224323272705s
Availability | VoID file availability check for SweFN-RDF took 0.0006661415100097656s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2732682228088379s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for SweFN-RDF took 5.7220458984375e-06s
INFO | --- Analysis for swefn-rdf took 6.078689098358154s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.124641418457031e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.2564725875854492s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 4.315376281738281e-05s
Believability | Calculation of trust value for SwetoDblp took 6.9141387939453125e-06s
INFO | --- Analysis for sweto-dblp took 22.759931564331055s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.6346640586853027s
Availability | VoID file availability check for Swift Vocabulary took 0.0006690025329589844s
Extra | Recovery of all triples for Swift Vocabulary took 2.229166269302368s
Performance | Total latancy measurement for Swift Vocabulary took 0.9983747005462646s
Amount of data | Number of triples check for Swift Vocabulary took 0.17435908317565918s
Interoperability | New terms check for Swift Vocabulary took 1.3281304836273193s
Versatility | Languages check for Swift Vocabulary took 0.17699122428894043s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.19106268882751465s
Interpretability | RDF structures check for Swift Vocabulary took 0.19288015365600586s
Versatility | Serialization formats check for Swift Vocabulary took 0.16159534454345703s
Availability | RDF dump link check for Swift Vocabulary took 0.1732187271118164s
License | MR license check for Swift Vocabulary took 0.16067886352539062s
License | HR license check for Swift Vocabulary took 0.1573472023010254s
Amount of data | Number of property check for Swift Vocabulary took 0.17548513412475586s
Understandability | Number of label check for Swift Vocabulary took 0.16644954681396484s
Understandability | URI regex check for Swift Vocabulary took 0.34394168853759766s
Understandability | Vocabs check for Swift Vocabulary took 0.17579960823059082s
Verifiability | Authors check for Swift Vocabulary took 0.17455339431762695s
Verifiability | Publishers check for Swift Vocabulary took 0.17006683349609375s
Performance | Throughput check for Swift Vocabulary took 10.468087673187256s
Amount of data | Check the number of entities for Swift Vocabulary took 8.320808410644531e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.19235467910766602s
Interlinking | sameAs chians check for Swift Vocabulary took 0.21124482154846191s
Interlinking | skos check for Swift Vocabulary took 0.21217751502990723s
Interlinking | skos check for Swift Vocabulary took 0.21127843856811523s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.2298440933227539s
Currency | Creation date check for Swift Vocabulary took 0.4250752925872803s
Currency | Modification date check for Swift Vocabulary took 0.41015076637268066s
Rep.Conc. | URIs length for Swift Vocabulary took 0.8429460525512695s
Interoperability | New vocabularies check for Swift Vocabulary took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.2085742950439453s
Accuracy | Check Functional Property for Swift Vocabulary took 0.21068787574768066s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.1925525665283203s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.3733794689178467s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0029976367950439453s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.0387570858001709s
Consistency | Disjoint class check for Swift Vocabulary took 0.2282116413116455s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.48326730728149414s
Consistency | Misplaced classes for Swift Vocabulary took 0.26399707794189453s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.3760480880737305s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.1367695331573486s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.3250081539154053s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.02767205238342285s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.1703348159790039s
Security | Sign check for Swift Vocabulary took 0.18846368789672852s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 1001.6266531944275s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.9168343544006348s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020858049392700195s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 0.00011754035949707031s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 1.1920928955078125e-06s
Believability | Calculation of trust value for Swift Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for Swift took 1047.7801249027252s
Availability | SPARQL endpoint availability check for SymbolicData took 6.794929504394531e-05s
Availability | VoID file availability check for SymbolicData took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.7123987674713135s
Reputation | Calculation of the PageRank for SymbolicData took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.24249267578125e-05s
Believability | Calculation of trust value for SymbolicData took 8.344650268554688e-06s
INFO | --- Analysis for symbolicdata took 4.846716642379761s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 5.7220458984375e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0007417201995849609s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.28792309761047363s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020954608917236328s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.790855407714844e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 6.9141387939453125e-06s
INFO | --- Analysis for symptoms-in-chinese took 53.28735160827637s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.41506099700927734s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0005588531494140625s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4625217914581299s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8736188411712646s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.980310916900635s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 23.340355396270752s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.18381381034851074s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 7.410973310470581s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 1.1334927082061768s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 2.572354316711426s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.5842657089233398s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.1782999038696289s
License | MR license check for National Digital Data Archive of Hungary (partial) took 1.19584059715271s
License | HR license check for National Digital Data Archive of Hungary (partial) took 60.50101637840271s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 1.5193099975585938s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 36.220468044281006s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.36336350440979004s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.1777815818786621s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.18054819107055664s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.4016294479370117s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.220337867736816s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 6.198883056640625e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.5710029602050781s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.774946928024292s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.4687340259552002s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.4142944812774658s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 0.16394495964050293s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 1.7123193740844727s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 0.3898918628692627s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 67.42952418327332s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.1894829273223877s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.25275421142578125s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0012106895446777344s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.0013642311096191406s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.1982579231262207s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 48.10022950172424s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.4971451759338379s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.4600298404693604s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.1813037395477295s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 52.13757824897766s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002210378646850586s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.2435317039489746s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.19587397575378418s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 12.282758951187134s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.5173189640045166s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.021210193634033203s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.5367431640625e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.9073486328125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.3909759521484375e-06s
INFO | --- Analysis for sztaki-lod took 502.1870172023773s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.38690185546875e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.27019524574279785s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020804882049560547s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 4.982948303222656e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 7.152557373046875e-06s
INFO | --- Analysis for t4gm-info took 39.00574493408203s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.410743713378906e-05s
Availability | VoID file availability check for tags2con delicious took 0.0008151531219482422s
Completeness | Calculation of interlinking completeness for tags2con delicious took 1.2375898361206055s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02332615852355957s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.363059997558594e-05s
Believability | Calculation of trust value for tags2con delicious took 7.152557373046875e-06s
INFO | --- Analysis for tags2con-delicious took 846.7047724723816s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 262.67579674720764s
Availability | VoID file availability check for Taiwan geographic names took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.31113123893737793s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.151199340820312e-05s
Believability | Calculation of trust value for Taiwan geographic names took 7.152557373046875e-06s
INFO | --- Analysis for taiwan-geographic-names took 667.6150586605072s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 8.940696716308594e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.26293349266052246s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020839691162109375s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 0.00010466575622558594s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.3909759521484375e-06s
INFO | --- Analysis for talis-openlibrary took 7.275846004486084s
Availability | SPARQL endpoint availability check for TalkBank took 8.082389831542969e-05s
Availability | VoID file availability check for TalkBank took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for TalkBank took 0.28386592864990234s
Reputation | Calculation of the PageRank for TalkBank took 0.020389795303344727s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.956390380859375e-05s
Believability | Calculation of trust value for TalkBank took 8.344650268554688e-06s
INFO | --- Analysis for talkbank took 4.758063316345215s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 1.5194470882415771s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.28647899627685547s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00011944770812988281s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 6.67572021484375e-06s
INFO | --- Analysis for taxonconcept took 15.774873733520508s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.38690185546875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0006122589111328125s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.27035069465637207s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.130073547363281e-05s
Believability | Calculation of trust value for taxonconcept-assets took 7.62939453125e-06s
INFO | --- Analysis for taxonconcept-assets took 2.875288963317871s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.38690185546875e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.2819666862487793s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.021271467208862305s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.001016855239868164s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 6.580352783203125e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 6.67572021484375e-06s
INFO | --- Analysis for taxonconcept-occurences took 3.223395824432373s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.442488431930542s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.00029277801513671875s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2462611198425293s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.673004150390625e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 6.4373016357421875e-06s
INFO | --- Analysis for taxref-ld took 7.832693576812744s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 262.49538016319275s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006511211395263672s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.2874281406402588s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.022901535034179688s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.361701965332031e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 6.9141387939453125e-06s
INFO | --- Analysis for tcga took 542.9738962650299s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.3569626808166504s
Availability | VoID file availability check for TCGA Roadmap took 0.00036597251892089844s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.26824140548706055s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.987022399902344e-05s
Believability | Calculation of trust value for TCGA Roadmap took 6.67572021484375e-06s
INFO | --- Analysis for tcga-roadmap took 10.29871129989624s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 1.7471721172332764s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.7875797748565674s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00010728836059570312s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.0967254638671875e-05s
INFO | --- Analysis for tcmgenedit_dataset took 142.80886101722717s
Availability | SPARQL endpoint availability check for TDS took 4.3392181396484375e-05s
Availability | VoID file availability check for TDS took 0.0006787776947021484s
Completeness | Calculation of interlinking completeness for TDS took 0.2634611129760742s
Reputation | Calculation of the PageRank for TDS took 0.020501136779785156s
Interlinking | Calculation of Degree of Connection for TDS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TDS took 0.0008907318115234375s
Interlinking | Calculation of Clustering coefficient for TDS took 4.2438507080078125e-05s
Believability | Calculation of trust value for TDS took 6.9141387939453125e-06s
INFO | --- Analysis for tds took 7.187226295471191s
Availability | SPARQL endpoint availability check for TED Talks took 4.172325134277344e-05s
Availability | VoID file availability check for TED Talks took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for TED Talks took 0.2562999725341797s
Reputation | Calculation of the PageRank for TED Talks took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for TED Talks took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TED Talks took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.7894973754882812e-05s
Believability | Calculation of trust value for TED Talks took 8.821487426757812e-06s
INFO | --- Analysis for ted-talks took 3.264321804046631s
Availability | SPARQL endpoint availability check for TEKORD took 8.058547973632812e-05s
Availability | VoID file availability check for TEKORD took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2647213935852051s
Reputation | Calculation of the PageRank for TEKORD took 0.02108621597290039s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0009601116180419922s
Interlinking | Calculation of Clustering coefficient for TEKORD took 5.626678466796875e-05s
Believability | Calculation of trust value for TEKORD took 7.3909759521484375e-06s
INFO | --- Analysis for tekord took 5.026791334152222s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 2.817007303237915s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.25751304626464844s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010919570922851562s
Believability | Calculation of trust value for Telegraphis Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for telegraphis took 9.609049320220947s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.9591064453125e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0007064342498779297s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2893400192260742s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.200241088867188e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 8.344650268554688e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 13.528635025024414s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.26848483085632324s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 2.9802322387695312e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.889936685562134s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.220008850097656e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.28731751441955566s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.8371810913085938e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for terminesp took 3.30441951751709s
Availability | SPARQL endpoint availability check for Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Ontology took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Ontology took 0.2573361396789551s
Reputation | Calculation of the PageRank for Ontology took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for Terrorist_attack took 2.8113203048706055s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.2438507080078125e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.26251912117004395s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020242691040039062s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 6.198883056640625e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.4174721240997314s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 5.650520324707031e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.26941394805908203s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.86102294921875e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 7.3909759521484375e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.9413652420043945s
Availability | SPARQL endpoint availability check for Teseo took 4.1484832763671875e-05s
Availability | VoID file availability check for Teseo took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Teseo took 0.25844502449035645s
Reputation | Calculation of the PageRank for Teseo took 0.020323991775512695s
Interlinking | Calculation of Degree of Connection for Teseo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Teseo took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Teseo took 2.8848648071289062e-05s
Believability | Calculation of trust value for Teseo took 7.3909759521484375e-06s
INFO | --- Analysis for teseo took 2.966353416442871s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.267692565917969e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.00035381317138671875s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2629687786102295s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.7894973754882812e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 6.4373016357421875e-06s
INFO | --- Analysis for Tesla_Deaths took 4.4887237548828125s
Availability | SPARQL endpoint availability check for test took 4.410743713378906e-05s
Availability | VoID file availability check for test took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for test took 0.24908900260925293s
Reputation | Calculation of the PageRank for test took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for test took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for test took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for test took 2.8371810913085938e-05s
Believability | Calculation of trust value for test took 8.106231689453125e-06s
INFO | --- Analysis for test took 2.319084882736206s
Availability | SPARQL endpoint availability check for Test took 4.315376281738281e-05s
Availability | VoID file availability check for Test took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Test took 0.25466346740722656s
Reputation | Calculation of the PageRank for Test took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Test took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Test took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Test took 2.8371810913085938e-05s
Believability | Calculation of trust value for Test took 7.3909759521484375e-06s
INFO | --- Analysis for Test took 2.3212873935699463s
Availability | SPARQL endpoint availability check for test-svu took 20.198094844818115s
Availability | VoID file availability check for test-svu took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for test-svu took 0.2739393711090088s
Reputation | Calculation of the PageRank for test-svu took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for test-svu took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for test-svu took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for test-svu took 2.8133392333984375e-05s
Believability | Calculation of trust value for test-svu took 6.198883056640625e-06s
INFO | --- Analysis for test-svu took 52.564637899398804s
Availability | SPARQL endpoint availability check for Test took 4.315376281738281e-05s
Availability | VoID file availability check for Test took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Test took 0.2705724239349365s
Reputation | Calculation of the PageRank for Test took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for Test took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Test took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Test took 3.7670135498046875e-05s
Believability | Calculation of trust value for Test took 5.0067901611328125e-06s
INFO | --- Analysis for Test_ took 2.4441287517547607s
Availability | SPARQL endpoint availability check for xxxxx took 262.13520669937134s
Availability | VoID file availability check for xxxxx took 0.0008168220520019531s
Completeness | Calculation of interlinking completeness for xxxxx took 0.9126431941986084s
Reputation | Calculation of the PageRank for xxxxx took 0.021154165267944336s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for xxxxx took 0.0001201629638671875s
Believability | Calculation of trust value for xxxxx took 6.4373016357421875e-06s
INFO | --- Analysis for testee took 799.2490742206573s
Availability | SPARQL endpoint availability check for Texai Lexicon took 6.103515625e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.7223010063171387s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 2.956390380859375e-05s
Believability | Calculation of trust value for Texai Lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for texai_lexicon took 6.67197847366333s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.315376281738281e-05s
Availability | VoID file availability check for tharawat magazine took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.2668616771697998s
Reputation | Calculation of the PageRank for tharawat magazine took 0.020718097686767578s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00013327598571777344s
Believability | Calculation of trust value for tharawat magazine took 6.4373016357421875e-06s
INFO | --- Analysis for tharawat-magazine-com took 4.327880382537842s
Availability | SPARQL endpoint availability check for The CIARD RING took 7.05718994140625e-05s
Availability | VoID file availability check for The CIARD RING took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.2560000419616699s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020615577697753906s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0279159545898438e-05s
Believability | Calculation of trust value for The CIARD RING took 6.4373016357421875e-06s
INFO | --- Analysis for the-ciard-ring took 3.4213030338287354s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.15438389778137207s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.281536340713501s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.075599670410156e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 6.4373016357421875e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 3.0918962955474854s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.8579978942871094s
Availability | VoID file availability check for The European Library Open Dataset took 0.0007166862487792969s
Extra | Recovery of all triples for The European Library Open Dataset took 1.4965488910675049s
Performance | Total latancy measurement for The European Library Open Dataset took 1.3533008098602295s
Amount of data | Number of triples check for The European Library Open Dataset took 30.210997581481934s
Versatility | Languages check for The European Library Open Dataset took 0.26633715629577637s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.25191617012024s
Interpretability | RDF structures check for The European Library Open Dataset took 0.3582015037536621s
Versatility | Serialization formats check for The European Library Open Dataset took 0.3110973834991455s
Availability | RDF dump link check for The European Library Open Dataset took 0.2880120277404785s
License | MR license check for The European Library Open Dataset took 0.9282026290893555s
License | HR license check for The European Library Open Dataset took 0.2996702194213867s
Amount of data | Number of property check for The European Library Open Dataset took 0.23663663864135742s
Understandability | Number of label check for The European Library Open Dataset took 3.4178595542907715s
Understandability | URI regex check for The European Library Open Dataset took 0.5169174671173096s
Understandability | Vocabs check for The European Library Open Dataset took 0.2575953006744385s
Verifiability | Authors check for The European Library Open Dataset took 0.26990342140197754s
Verifiability | Publishers check for The European Library Open Dataset took 0.28112077713012695s
Performance | Throughput check for The European Library Open Dataset took 11.755297183990479s
Amount of data | Check the number of entities for The European Library Open Dataset took 5.984306335449219e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.24348211288452148s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.3086519241333008s
Interlinking | skos check for The European Library Open Dataset took 0.9989805221557617s
Interlinking | skos check for The European Library Open Dataset took 0.2455754280090332s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.2839994430541992s
Currency | Creation date check for The European Library Open Dataset took 0.45562243461608887s
Currency | Modification date check for The European Library Open Dataset took 1.0214078426361084s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.50349426269531s
Interoperability | New vocabularies check for The European Library Open Dataset took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.23288941383361816s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 1.024303913116455s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.027860641479492188s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02757883071899414s
Consistency | Disjoint class check for The European Library Open Dataset took 0.28771066665649414s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.534297943115234s
Consistency | Misplaced classes for The European Library Open Dataset took 0.32402658462524414s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.6809732913970947s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.14154052734375s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.345763444900513s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03246283531188965s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.29064393043518066s
Security | Sign check for The European Library Open Dataset took 0.3319122791290283s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 10.946972131729126s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.44878077507019043s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 5.5789947509765625e-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 8.821487426757812e-06s
INFO | --- Analysis for the-european-library-open-dataset took 404.46672558784485s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.05711078643799s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0008068084716796875s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.7128262519836426s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010538101196289062s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for the-eurostat-linked-data took 244.8673872947693s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.414817810058594e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002799034118652344s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.24770402908325195s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.4809112548828125e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.867813110351562e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 5.263697385787964s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.458427429199219e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0003578662872314453s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.8920750617980957s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.963180541992188e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 6.67572021484375e-06s
INFO | --- Analysis for the-living-lod-cloud took 52.425352811813354s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 8.58306884765625e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2654304504394531s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 3.170967102050781e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 6.4373016357421875e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.762392044067383s
Availability | SPARQL endpoint availability check for The View From took 0.0957190990447998s
Availability | VoID file availability check for The View From took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for The View From took 0.2538931369781494s
Reputation | Calculation of the PageRank for The View From took 0.020824909210205078s
Interlinking | Calculation of Degree of Connection for The View From took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for The View From took 8.869171142578125e-05s
Believability | Calculation of trust value for The View From took 8.344650268554688e-06s
INFO | --- Analysis for the-view-from took 3.0305662155151367s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.599589586257935s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.28699207305908203s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020800352096557617s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007381439208984375s
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 7.3909759521484375e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.70044732093811s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 29.99943494796753s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0008008480072021484s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.716937780380249s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020349502563476562s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 3.0279159545898438e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.152557373046875e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 103.15177154541016s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.5299530029296875e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2737293243408203s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00011324882507324219s
Believability | Calculation of trust value for The Content Wrangler took 6.67572021484375e-06s
INFO | --- Analysis for thecontentwrangler-com took 4.43949294090271s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.100799560546875e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.28522157669067383s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.0212249755859375s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0008931159973144531s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.62396240234375e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.867813110351562e-06s
INFO | --- Analysis for thesaurus-bncf took 2.9241511821746826s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.315376281738281e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.25911426544189453s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.0205385684967041s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.24249267578125e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 6.9141387939453125e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.463092803955078s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.46289849281311035s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0005896091461181641s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.27378273010253906s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.020372629165649414s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.700920104980469e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 7.62939453125e-06s
INFO | --- Analysis for thesaurus-w took 4.400112867355347s
Availability | SPARQL endpoint availability check for theses.fr took 4.5299530029296875e-05s
Availability | VoID file availability check for theses.fr took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for theses.fr took 0.36848020553588867s
Reputation | Calculation of the PageRank for theses.fr took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for theses.fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for theses.fr took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.982948303222656e-05s
Believability | Calculation of trust value for theses.fr took 7.867813110351562e-06s
INFO | --- Analysis for thesesfr took 4.994389533996582s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 5.078315734863281e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.26993441581726074s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.457069396972656e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 6.198883056640625e-06s
INFO | --- Analysis for Thinkphile took 2.4090347290039062s
Availability | SPARQL endpoint availability check for ThIST took 267.02413988113403s
Availability | VoID file availability check for ThIST took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for ThIST took 0.2996835708618164s
Reputation | Calculation of the PageRank for ThIST took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for ThIST took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.440017700195312e-05s
Believability | Calculation of trust value for ThIST took 6.67572021484375e-06s
INFO | --- Analysis for thist took 570.5714197158813s
Availability | SPARQL endpoint availability check for TIP took 40.03082990646362s
Availability | VoID file availability check for TIP took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for TIP took 0.7211453914642334s
Reputation | Calculation of the PageRank for TIP took 0.021141529083251953s
Interlinking | Calculation of Degree of Connection for TIP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00011539459228515625s
Believability | Calculation of trust value for TIP took 7.62939453125e-06s
INFO | --- Analysis for tip took 104.63518595695496s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.506111145019531e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0006716251373291016s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.7098543643951416s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02069997787475586s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.123283386230469e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.0013580322265625e-05s
INFO | --- Analysis for TOPMODEL took 23.182719945907593s
Availability | SPARQL endpoint availability check for Tourpedia took 4.267692565917969e-05s
Availability | VoID file availability check for Tourpedia took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.2848985195159912s
Reputation | Calculation of the PageRank for Tourpedia took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.00103759765625s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.933906555175781e-05s
Believability | Calculation of trust value for Tourpedia took 9.059906005859375e-06s
INFO | --- Analysis for tourpedia took 5.107806921005249s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.3899128437042236s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.7259676456451416s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020845651626586914s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.5762786865234375e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 8.821487426757812e-06s
INFO | --- Analysis for TP-data took 7.6985273361206055s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 1.7494919300079346s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0007643699645996094s
Extra | Recovery of all triples for Trackloaded Linked Open Data took 2.90727162361145s
Performance | Total latancy measurement for Trackloaded Linked Open Data took 1.9463222026824951s
Amount of data | Number of triples check for Trackloaded Linked Open Data took 1.725348711013794s
Interoperability | New terms check for Trackloaded Linked Open Data took 3.1083383560180664s
Versatility | Languages check for Trackloaded Linked Open Data took 3.7405037879943848s
Interpretability | Number of blank nodes check for Trackloaded Linked Open Data took 2.545891523361206s
Interpretability | RDF structures check for Trackloaded Linked Open Data took 1.9847412109375s
Versatility | Serialization formats check for Trackloaded Linked Open Data took 1.8931269645690918s
Availability | RDF dump link check for Trackloaded Linked Open Data took 3.0134918689727783s
License | MR license check for Trackloaded Linked Open Data took 2.9139137268066406s
License | HR license check for Trackloaded Linked Open Data took 1.6462466716766357s
Amount of data | Number of property check for Trackloaded Linked Open Data took 1.9220695495605469s
Understandability | Number of label check for Trackloaded Linked Open Data took 2.4255940914154053s
Understandability | URI regex check for Trackloaded Linked Open Data took 3.7284560203552246s
Understandability | Vocabs check for Trackloaded Linked Open Data took 1.7575888633728027s
Verifiability | Authors check for Trackloaded Linked Open Data took 1.7807462215423584s
Verifiability | Publishers check for Trackloaded Linked Open Data took 2.004380702972412s
Performance | Throughput check for Trackloaded Linked Open Data took 23.701877117156982s
Amount of data | Check the number of entities for Trackloaded Linked Open Data took 7.796287536621094e-05s
Verifiability | Contribs. check for Trackloaded Linked Open Data took 2.886384963989258s
Interlinking | sameAs chians check for Trackloaded Linked Open Data took 2.1520936489105225s
Interlinking | skos check for Trackloaded Linked Open Data took 1.9439780712127686s
Interlinking | skos check for Trackloaded Linked Open Data took 0.3178527355194092s
Timeliness | dataset update frequency check for Trackloaded Linked Open Data took 2.1859686374664307s
Currency | Creation date check for Trackloaded Linked Open Data took 3.5735135078430176s
Currency | Modification date check for Trackloaded Linked Open Data took 24.086020469665527s
Rep.Conc. | URIs length for Trackloaded Linked Open Data took 3.6768798828125s
Interoperability | New vocabularies check for Trackloaded Linked Open Data took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Linked Open Data took 1.972578525543213s
Consistency | Disjoint class check for Trackloaded Linked Open Data took 1.7912249565124512s
Consistency | Check Misplaced properties for Trackloaded Linked Open Data took 4.013916730880737s
Consistency | Check Ontology hijacking for Trackloaded Linked Open Data took 3.1985929012298584s
Consistency | Check Invalid usage of undefined properties for Trackloaded Linked Open Data took 1.4575395584106445s
Security | Sign check for Trackloaded Linked Open Data took 1.6649315357208252s
Availability | Check URIs Dereferenciability for Trackloaded Linked Open Data took 1.7776474952697754s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.24423813819885254s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 3.790855407714844e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Linked Open Data took 1.9073486328125e-06s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 7.152557373046875e-06s
