Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.4345855712890625e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.7407302856445312s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.45002317428588867s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00040078163146972656s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 6.9141387939453125e-06s
INFO | --- Analysis for 0080-3626 took 6.0355446338653564s
Availability | SPARQL endpoint availability check for 土地利用图 took 4.363059997558594e-05s
Availability | VoID file availability check for 土地利用图 took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.6989169120788574s
Reputation | Calculation of the PageRank for 土地利用图 took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 3.170967102050781e-05s
Believability | Calculation of trust value for 土地利用图 took 7.152557373046875e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 3.304490804672241s
Availability | SPARQL endpoint availability check for 113322 took 4.172325134277344e-05s
Availability | VoID file availability check for 113322 took 0.0008754730224609375s
Completeness | Calculation of interlinking completeness for 113322 took 0.28578996658325195s
Reputation | Calculation of the PageRank for 113322 took 0.02869105339050293s
Interlinking | Calculation of Degree of Connection for 113322 took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0016036033630371094s
Interlinking | Calculation of Clustering coefficient for 113322 took 4.291534423828125e-05s
Believability | Calculation of trust value for 113322 took 7.867813110351562e-06s
INFO | --- Analysis for 11 took 4.9156718254089355s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 5.817413330078125e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.2907381057739258s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.0199887752532959s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.9325485229492188e-05s
Believability | Calculation of trust value for Korepetycje Buki took 7.867813110351562e-06s
INFO | --- Analysis for 12323 took 2.4329330921173096s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.07468652725219727s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2814922332763672s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.020838022232055664s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 9.393692016601562e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 7.62939453125e-06s
INFO | --- Analysis for 2000-us-census-rdf took 3.315185546875s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 2.1384572982788086s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005619525909423828s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.2709643840789795s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.02001810073852539s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.6716461181640625e-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 6.798717021942139s
Availability | SPARQL endpoint availability check for Open Data Web took 0.6923253536224365s
Availability | VoID file availability check for Open Data Web took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.268770694732666s
Reputation | Calculation of the PageRank for Open Data Web took 0.020275115966796875s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.1961669921875e-05s
Believability | Calculation of trust value for Open Data Web took 7.62939453125e-06s
INFO | --- Analysis for _data.odw.tw took 3.1234376430511475s
Availability | SPARQL endpoint availability check for 土地利用 took 7.271766662597656e-05s
Availability | VoID file availability check for 土地利用 took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2868461608886719s
Reputation | Calculation of the PageRank for 土地利用 took 0.0198819637298584s
Interlinking | Calculation of Degree of Connection for 土地利用 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.7418136596679688e-05s
Believability | Calculation of trust value for 土地利用 took 7.152557373046875e-06s
INFO | --- Analysis for _data1.odw.tw took 2.4099385738372803s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.363059997558594e-05s
Availability | VoID file availability check for 土地利用模型 took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.2695329189300537s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020132780075073242s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 土地利用模型 took 6.67572021484375e-06s
INFO | --- Analysis for _data2.odw.tw took 5.325052738189697s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.410743713378906e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0006380081176757812s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2783393859863281s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0009157657623291016s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.504753112792969e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 3.824432611465454s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.267692565917969e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0005910396575927734s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.2765474319458008s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.019992589950561523s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0009262561798095703s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 3.314018249511719e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 6.9141387939453125e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 3.049093246459961s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.172325134277344e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.0007030963897705078s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.26403093338012695s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.02024102210998535s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.8133392333984375e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 5.4836273193359375e-06s
INFO | --- Analysis for A1 took 3.2810680866241455s
Availability | SPARQL endpoint availability check for SummerOlympics took 5.164639234542847s
Availability | VoID file availability check for SummerOlympics took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.24618744850158691s
Reputation | Calculation of the PageRank for SummerOlympics took 0.02002406120300293s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.556510925292969e-05s
Believability | Calculation of trust value for SummerOlympics took 1.0967254638671875e-05s
INFO | --- Analysis for abc took 21.89535403251648s
Availability | SPARQL endpoint availability check for Test_m took 4.267692565917969e-05s
Availability | VoID file availability check for Test_m took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Test_m took 0.25925755500793457s
Reputation | Calculation of the PageRank for Test_m took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Test_m took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Test_m took 3.0279159545898438e-05s
Believability | Calculation of trust value for Test_m took 7.152557373046875e-06s
INFO | --- Analysis for ABC took 2.3711328506469727s
Availability | SPARQL endpoint availability check for my intro took 4.172325134277344e-05s
Availability | VoID file availability check for my intro took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for my intro took 0.254223108291626s
Reputation | Calculation of the PageRank for my intro took 0.0199735164642334s
Interlinking | Calculation of Degree of Connection for my intro took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for my intro took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for my intro took 2.8133392333984375e-05s
Believability | Calculation of trust value for my intro took 8.106231689453125e-06s
INFO | --- Analysis for abhay_intro took 2.397796154022217s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.45879602432250977s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.25168514251708984s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.019887447357177734s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 0.00010085105895996094s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for abs-linked-data took 2.834526777267456s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 5.221366882324219e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.26761555671691895s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.0199892520904541s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 3.0279159545898438e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 6.67572021484375e-06s
INFO | --- Analysis for academic-offer-of-unl took 3.3792388439178467s
Availability | SPARQL endpoint availability check for AcadOnto took 4.3392181396484375e-05s
Availability | VoID file availability check for AcadOnto took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.27268171310424805s
Reputation | Calculation of the PageRank for AcadOnto took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for AcadOnto took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.8371810913085938e-05s
Believability | Calculation of trust value for AcadOnto took 7.867813110351562e-06s
INFO | --- Analysis for acadonto took 2.906043529510498s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 10.510509252548218s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.26094913482666016s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0199735164642334s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.457069396972656e-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 36.42780351638794s
Availability | SPARQL endpoint availability check for Addgene took 4.267692565917969e-05s
Availability | VoID file availability check for Addgene took 0.0008029937744140625s
Completeness | Calculation of interlinking completeness for Addgene took 0.26918745040893555s
Reputation | Calculation of the PageRank for Addgene took 0.020157337188720703s
Interlinking | Calculation of Degree of Connection for Addgene took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.695487976074219e-05s
Believability | Calculation of trust value for Addgene took 1.0728836059570312e-05s
INFO | --- Analysis for addgene took 16.342127084732056s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.1961669921875e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.0007996559143066406s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2560758590698242s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.020721435546875s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0009868144989013672s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 0.00011014938354492188s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 7.3909759521484375e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 7.372913122177124s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 0.7300548553466797s
Availability | VoID file availability check for AEMET metereological dataset took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.26877260208129883s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0009961128234863281s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 5.0067901611328125e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.867813110351562e-06s
INFO | --- Analysis for aemet took 6.8164191246032715s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.076957702636719e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.27806925773620605s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.021431684494018555s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.266334533691406e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 8.58306884765625e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.967367649078369s
Availability | SPARQL endpoint availability check for AgriNepalData took 0.031630754470825195s
Availability | VoID file availability check for AgriNepalData took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.2650299072265625s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020446062088012695s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 0.00010561943054199219s
Believability | Calculation of trust value for AgriNepalData took 8.58306884765625e-06s
INFO | --- Analysis for agrinepaldata took 2.4742250442504883s
Availability | SPARQL endpoint availability check for AGRIS took 262.83719635009766s
Availability | VoID file availability check for AGRIS took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for AGRIS took 0.29450368881225586s
Reputation | Calculation of the PageRank for AGRIS took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for AGRIS took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for AGRIS took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.535385131835938e-05s
Believability | Calculation of trust value for AGRIS took 1.3113021850585938e-05s
INFO | --- Analysis for agris took 557.5593888759613s
Availability | SPARQL endpoint availability check for AGROVOC took 0.18573379516601562s
Availability | VoID file availability check for AGROVOC took 0.0005984306335449219s
Extra | Recovery of all triples for AGROVOC took 33.15042161941528s
Performance | Total latancy measurement for AGROVOC took 0.4319882392883301s
Amount of data | Number of triples check for AGROVOC took 30.084659337997437s
Interoperability | New terms check for AGROVOC took 3.986969232559204s
Versatility | Languages check for AGROVOC took 30.0845205783844s
Interpretability | Number of blank nodes check for AGROVOC took 30.08697271347046s
Interpretability | RDF structures check for AGROVOC took 0.10743331909179688s
Versatility | Serialization formats check for AGROVOC took 0.1000359058380127s
Availability | RDF dump link check for AGROVOC took 0.0881340503692627s
License | MR license check for AGROVOC took 0.08834052085876465s
License | HR license check for AGROVOC took 0.898963451385498s
Amount of data | Number of property check for AGROVOC took 0.08924722671508789s
Understandability | Number of label check for AGROVOC took 30.08707356452942s
Understandability | URI regex check for AGROVOC took 0.1883106231689453s
Understandability | Vocabs check for AGROVOC took 0.08187246322631836s
Verifiability | Authors check for AGROVOC took 0.09512877464294434s
Verifiability | Publishers check for AGROVOC took 0.08625435829162598s
Performance | Throughput check for AGROVOC took 10.480238199234009s
Amount of data | Check the number of entities for AGROVOC took 0.00010395050048828125s
Verifiability | Contribs. check for AGROVOC took 0.0904233455657959s
Interlinking | sameAs chians check for AGROVOC took 0.09124326705932617s
Interlinking | skos check for AGROVOC took 16.59217143058777s
Interlinking | skos check for AGROVOC took 13.460747003555298s
Timeliness | dataset update frequency check for AGROVOC took 0.09009003639221191s
Currency | Creation date check for AGROVOC took 0.16810965538024902s
Currency | Modification date check for AGROVOC took 0.17700910568237305s
Rep.Conc. | URIs length for AGROVOC took 50.50603723526001s
Interoperability | New vocabularies check for AGROVOC took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for AGROVOC took 0.09737563133239746s
Accuracy | Check Empty annotation labels for AGROVOC took 16.249885082244873s
Accuracy | Check White space in annotation for AGROVOC took 3.005854845046997s
Consistency | Disjoint class check for AGROVOC took 0.08498048782348633s
Consistency | Check Misplaced properties for AGROVOC took 21.18375062942505s
Consistency | Check Ontology hijacking for AGROVOC took 30.104419469833374s
Consistency | Check Invalid usage of undefined properties for AGROVOC took 23.017321348190308s
Conciseness | Check Extensional conciseness for AGROVOC took 0.0001647472381591797s
Conciseness | Check Intensional conciseness for AGROVOC took 0.07651662826538086s
Security | Sign check for AGROVOC took 0.08956742286682129s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.8158199787139893s
Reputation | Calculation of the PageRank for AGROVOC took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.0001125335693359375s
Interoperability | Check the re-using of existing vocabs for AGROVOC took 1.9073486328125e-06s
Believability | Calculation of trust value for AGROVOC took 7.62939453125e-06s
INFO | --- Analysis for agrovoc took 421.0309360027313s
Availability | SPARQL endpoint availability check for AGROVOC took 4.1484832763671875e-05s
Availability | VoID file availability check for AGROVOC took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.2800750732421875s
Reputation | Calculation of the PageRank for AGROVOC took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 6.246566772460938e-05s
Believability | Calculation of trust value for AGROVOC took 6.9141387939453125e-06s
INFO | --- Analysis for agrovoc-skos took 4.213825225830078s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 0.989116907119751s
Availability | VoID file availability check for Analytics India Magazine took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.296968936920166s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020425081253051758s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.0279159545898438e-05s
Believability | Calculation of trust value for Analytics India Magazine took 6.67572021484375e-06s
INFO | --- Analysis for AIM took 5.561349630355835s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.2438507080078125e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.24834179878234863s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02019357681274414s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.0994415283203125e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 7.62939453125e-06s
INFO | --- Analysis for AISHE took 2.3989908695220947s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.267692565917969e-05s
Availability | VoID file availability check for  equipment ontology took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.27007079124450684s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02017807960510254s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for  equipment ontology took 6.4373016357421875e-06s
INFO | --- Analysis for akash took 2.3821983337402344s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.029273986816406e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.2799532413482666s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020314693450927734s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 7.152557373046875e-06s
INFO | --- Analysis for aksworg took 3.3961002826690674s
Availability | SPARQL endpoint availability check for AlchemyAPI took 7.224082946777344e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.2817652225494385s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.123283386230469e-05s
Believability | Calculation of trust value for AlchemyAPI took 7.152557373046875e-06s
INFO | --- Analysis for alchemyapi took 2.8614046573638916s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.315376281738281e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.26735544204711914s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.019939422607421875s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.8371810913085938e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 8.106231689453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.883146047592163s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 2.8484580516815186s
Availability | VoID file availability check for aliada-scanbit-net took 0.0004334449768066406s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.2737095355987549s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020400285720825195s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00011515617370605469s
Believability | Calculation of trust value for aliada-scanbit-net took 7.62939453125e-06s
INFO | --- Analysis for aliada-scanbit-net took 6.227813959121704s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.172325134277344e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.26897644996643066s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.9802322387695312e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 8.821487426757812e-06s
INFO | --- Analysis for allen-brain-atlas took 2.836566209793091s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 1.3685972690582275s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.0006051063537597656s
Extra | Recovery of all triples for Allie Abbreviation And Long Form Database in Life Science took 147.7079041004181s
Performance | Total latancy measurement for Allie Abbreviation And Long Form Database in Life Science took 2.731271266937256s
Amount of data | Number of triples check for Allie Abbreviation And Long Form Database in Life Science took 1.482499361038208s
Interoperability | New terms check for Allie Abbreviation And Long Form Database in Life Science took 3.619560956954956s
Versatility | Languages check for Allie Abbreviation And Long Form Database in Life Science took 300.09961128234863s
Interpretability | Number of blank nodes check for Allie Abbreviation And Long Form Database in Life Science took 4.629865407943726s
Security | Check HTTPS for Allie Abbreviation And Long Form Database in Life Science took 1.8936798572540283s
Interpretability | RDF structures check for Allie Abbreviation And Long Form Database in Life Science took 0.7073554992675781s
Versatility | Serialization formats check for Allie Abbreviation And Long Form Database in Life Science took 0.7445132732391357s
Availability | RDF dump link check for Allie Abbreviation And Long Form Database in Life Science took 0.5757179260253906s
License | MR license check for Allie Abbreviation And Long Form Database in Life Science took 0.9122321605682373s
License | HR license check for Allie Abbreviation And Long Form Database in Life Science took 33.821598052978516s
Amount of data | Number of property check for Allie Abbreviation And Long Form Database in Life Science took 0.5730929374694824s
Understandability | Number of label check for Allie Abbreviation And Long Form Database in Life Science took 1.2502193450927734s
Understandability | URI regex check for Allie Abbreviation And Long Form Database in Life Science took 1.1139585971832275s
Understandability | Vocabs check for Allie Abbreviation And Long Form Database in Life Science took 0.607515811920166s
Verifiability | Authors check for Allie Abbreviation And Long Form Database in Life Science took 0.6100363731384277s
Verifiability | Publishers check for Allie Abbreviation And Long Form Database in Life Science took 0.5698871612548828s
Performance | Throughput check for Allie Abbreviation And Long Form Database in Life Science took 10.80748462677002s
Amount of data | Check the number of entities for Allie Abbreviation And Long Form Database in Life Science took 0.00012040138244628906s
Verifiability | Contribs. check for Allie Abbreviation And Long Form Database in Life Science took 0.5942337512969971s
Interlinking | sameAs chians check for Allie Abbreviation And Long Form Database in Life Science took 0.6045780181884766s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5906317234039307s
Interlinking | skos check for Allie Abbreviation And Long Form Database in Life Science took 0.5401105880737305s
Timeliness | dataset update frequency check for Allie Abbreviation And Long Form Database in Life Science took 0.6585729122161865s
Currency | Creation date check for Allie Abbreviation And Long Form Database in Life Science took 1.325505256652832s
Currency | Modification date check for Allie Abbreviation And Long Form Database in Life Science took 1.1105992794036865s
Rep.Conc. | URIs length for Allie Abbreviation And Long Form Database in Life Science took 57.01524209976196s
Interoperability | New vocabularies check for Allie Abbreviation And Long Form Database in Life Science took 4.208866119384766s
Consistency | Deprecated classes/propertiers check for Allie Abbreviation And Long Form Database in Life Science took 0.5564172267913818s
Accuracy | Check Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.6713309288024902s
Accuracy | Check Inverse Functional Property for Allie Abbreviation And Long Form Database in Life Science took 0.580374002456665s
Accuracy | Check Empty annotation labels for Allie Abbreviation And Long Form Database in Life Science took 40.4663462638855s
Accuracy | Check White space in annotation for Allie Abbreviation And Long Form Database in Life Science took 3.027467966079712s
Accuracy | Check Datatype consistency for Allie Abbreviation And Long Form Database in Life Science took 2.5762791633605957s
Consistency | Disjoint class check for Allie Abbreviation And Long Form Database in Life Science took 0.6149780750274658s
Consistency | Check Misplaced properties for Allie Abbreviation And Long Form Database in Life Science took 14.988029956817627s
Consistency | Misplaced classes for Allie Abbreviation And Long Form Database in Life Science took 8.731925249099731s
Consistency | Check Ontology hijacking for Allie Abbreviation And Long Form Database in Life Science took 40.811755895614624s
Consistency | Check Invalid usage of undefined classes for Allie Abbreviation And Long Form Database in Life Science took 1.4337208271026611s
Consistency | Check Invalid usage of undefined properties for Allie Abbreviation And Long Form Database in Life Science took 16.14302372932434s
Conciseness | Check Extensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 2.757359743118286s
Conciseness | Check Intensional conciseness for Allie Abbreviation And Long Form Database in Life Science took 0.8283464908599854s
Security | Sign check for Allie Abbreviation And Long Form Database in Life Science took 0.5384008884429932s
Availability | Check URIs Dereferenciability for Allie Abbreviation And Long Form Database in Life Science took 12776.828709363937s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 1.0675320625305176s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.022735118865966797s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 2.0265579223632812e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 0.00017547607421875s
Interoperability | Check the re-using of existing vocabs for Allie Abbreviation And Long Form Database in Life Science took 10.254556655883789s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 6.67572021484375e-06s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 13577.472928762436s
Availability | SPARQL endpoint availability check for Alojamientos took 4.482269287109375e-05s
Availability | VoID file availability check for Alojamientos took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.26686739921569824s
Reputation | Calculation of the PageRank for Alojamientos took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.790855407714844e-05s
Believability | Calculation of trust value for Alojamientos took 7.152557373046875e-06s
INFO | --- Analysis for alojamientos-zaragoza took 3.415891647338867s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 0.3007783889770508s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.2638723850250244s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.021388769149780273s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.790855407714844e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 6.9141387939453125e-06s
INFO | --- Analysis for alpino-rdf took 4.537652969360352s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.172325134277344e-05s
Availability | VoID file availability check for AAT-atawil took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.2889556884765625s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 2.9087066650390625e-05s
Believability | Calculation of trust value for AAT-atawil took 6.4373016357421875e-06s
INFO | --- Analysis for Altawil took 2.3575055599212646s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.00543212890625e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.2501688003540039s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 2.8848648071289062e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 6.4373016357421875e-06s
INFO | --- Analysis for am-collections-online took 2.926708936691284s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.291534423828125e-05s
Availability | VoID file availability check for Amer Nejma took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.2712273597717285s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.0040740966796875e-05s
Believability | Calculation of trust value for Amer Nejma took 6.67572021484375e-06s
INFO | --- Analysis for Amer_Nejma took 2.399407148361206s
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.0002295970916748047s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.26401805877685547s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for amon took 3.3738515377044678s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7977111339569092s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.2925589084625244s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0009627342224121094s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00011563301086425781s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 6.198883056640625e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.7794406414031982s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.076957702636719e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.2705066204071045s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.0201871395111084s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.0517578125e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 6.67572021484375e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.896455764770508s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.100799560546875e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.26114821434020996s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.02018594741821289s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.8848648071289062e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.198883056640625e-06s
INFO | --- Analysis for animal-diversity-web took 2.96502423286438s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for Anime Dataset took 0.0013620853424072266s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.2652890682220459s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020244836807250977s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Anime Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for Anime took 3.853825092315674s
Availability | SPARQL endpoint availability check for ANNO took 4.2438507080078125e-05s
Availability | VoID file availability check for ANNO took 0.0005948543548583984s
Completeness | Calculation of interlinking completeness for ANNO took 0.25780677795410156s
Reputation | Calculation of the PageRank for ANNO took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for ANNO took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ANNO took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.266334533691406e-05s
Believability | Calculation of trust value for ANNO took 9.059906005859375e-06s
INFO | --- Analysis for anno took 4.2160820960998535s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.172325134277344e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.2809903621673584s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020312786102294922s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.510185241699219e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 5.9604644775390625e-06s
INFO | --- Analysis for AntiqueCarsCollection took 3.453613519668579s
Availability | SPARQL endpoint availability check for apache took 4.315376281738281e-05s
Availability | VoID file availability check for apache took 0.0006642341613769531s
Completeness | Calculation of interlinking completeness for apache took 0.2676515579223633s
Reputation | Calculation of the PageRank for apache took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for apache took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for apache took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for apache took 5.2928924560546875e-05s
Believability | Calculation of trust value for apache took 6.4373016357421875e-06s
INFO | --- Analysis for apache took 3.270972728729248s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF took 0.0005381107330322266s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2715420722961426s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf took 5.490515232086182s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 9.72747802734375e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.2762317657470703s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020123958587646484s
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.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 5.656852722167969s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0007047653198242188s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.27002525329589844s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.020670652389526367s
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.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 7.867813110351562e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 5.673149347305298s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.124641418457031e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2618215084075928s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.02032160758972168s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.3392181396484375e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-en-es took 5.62157416343689s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0005877017974853516s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.2567875385284424s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.02041029930114746s
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.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 5.582851409912109s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.24408245086669922s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 5.653750419616699s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 5.698204040527344e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.00058746337890625s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.25207948684692383s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 5.6180620193481445s
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.0006694793701171875s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.27224278450012207s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 5.700282335281372s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.172325134277344e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.27210474014282227s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020241737365722656s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.982948303222656e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 5.59234356880188s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.696846008300781e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0006120204925537109s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2663881778717041s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-es-an took 5.609860897064209s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0005638599395751953s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.26995325088500977s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.6253204345703125e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 5.881903409957886s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 0.00011968612670898438s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.26973581314086914s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ca took 24.816246271133423s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.0013320446014404297s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.26103973388671875s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.02055072784423828s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.4345855712890625e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 5.574862241744995s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.29123592376708984s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 5.728644609451294s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.1961669921875e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0005650520324707031s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.25738000869750977s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 5.4387617111206055s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 4.267692565917969e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2558619976043701s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.02052927017211914s
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.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 5.516699314117432s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.4345855712890625e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.2645914554595947s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020085573196411133s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.626678466796875e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 5.655948638916016s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.27985334396362305s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.1920928955078125e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 5.574851989746094s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 6.67572021484375e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2791111469268799s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 5.587828874588013s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0007503032684326172s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.27163171768188477s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 5.51930046081543s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 4.3392181396484375e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0005927085876464844s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2791323661804199s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.021211862564086914s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 5.599506378173828s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.2438507080078125e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0007121562957763672s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2739078998565674s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 5.635390520095825s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 5.602836608886719e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.28294825553894043s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 5.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 6.241944074630737s
Availability | SPARQL endpoint availability check for AragoDBPedia took 0.7518982887268066s
Availability | VoID file availability check for AragoDBPedia took 0.0011372566223144531s
Extra | Recovery of all triples for AragoDBPedia took 3.1708908081054688s
Performance | Total latancy measurement for AragoDBPedia took 2.0095064640045166s
Amount of data | Number of triples check for AragoDBPedia took 0.7777419090270996s
Interoperability | New terms check for AragoDBPedia took 2.2092788219451904s
Versatility | Languages check for AragoDBPedia took 60.48373055458069s
Interpretability | Number of blank nodes check for AragoDBPedia took 4.870870351791382s
Security | Check HTTPS for AragoDBPedia took 0.24963855743408203s
Interpretability | RDF structures check for AragoDBPedia took 0.7306952476501465s
Versatility | Serialization formats check for AragoDBPedia took 1.0711476802825928s
Availability | RDF dump link check for AragoDBPedia took 0.41562867164611816s
License | MR license check for AragoDBPedia took 0.5852694511413574s
License | HR license check for AragoDBPedia took 6.444115877151489s
Amount of data | Number of property check for AragoDBPedia took 0.4116988182067871s
Understandability | Number of label check for AragoDBPedia took 0.4975721836090088s
Understandability | URI regex check for AragoDBPedia took 0.9023098945617676s
Understandability | Vocabs check for AragoDBPedia took 0.47463202476501465s
Verifiability | Authors check for AragoDBPedia took 0.4727976322174072s
Verifiability | Publishers check for AragoDBPedia took 0.4216499328613281s
Performance | Throughput check for AragoDBPedia took 11.763810634613037s
Amount of data | Check the number of entities for AragoDBPedia took 7.104873657226562e-05s
Verifiability | Contribs. check for AragoDBPedia took 0.4945499897003174s
Interlinking | sameAs chians check for AragoDBPedia took 0.4438035488128662s
Interlinking | skos check for AragoDBPedia took 0.5243871212005615s
Interlinking | skos check for AragoDBPedia took 0.37790799140930176s
Timeliness | dataset update frequency check for AragoDBPedia took 0.9718234539031982s
Currency | Creation date check for AragoDBPedia took 1.8785021305084229s
Currency | Modification date check for AragoDBPedia took 0.8466198444366455s
Rep.Conc. | URIs length for AragoDBPedia took 6.152333498001099s
Interoperability | New vocabularies check for AragoDBPedia took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for AragoDBPedia took 0.4188864231109619s
Accuracy | Check Functional Property for AragoDBPedia took 0.44913434982299805s
Accuracy | Check Inverse Functional Property for AragoDBPedia took 0.5049746036529541s
Accuracy | Check Empty annotation labels for AragoDBPedia took 1.1738688945770264s
Accuracy | Check White space in annotation for AragoDBPedia took 0.030248165130615234s
Accuracy | Check Datatype consistency for AragoDBPedia took 0.02748394012451172s
Consistency | Disjoint class check for AragoDBPedia took 0.3818783760070801s
Consistency | Check Misplaced properties for AragoDBPedia took 4.72611927986145s
Consistency | Misplaced classes for AragoDBPedia took 0.6512415409088135s
Consistency | Check Ontology hijacking for AragoDBPedia took 2.689117908477783s
Consistency | Check Invalid usage of undefined classes for AragoDBPedia took 1.3399806022644043s
Consistency | Check Invalid usage of undefined properties for AragoDBPedia took 5.364073991775513s
Conciseness | Check Extensional conciseness for AragoDBPedia took 0.03241252899169922s
Conciseness | Check Intensional conciseness for AragoDBPedia took 0.5880289077758789s
Security | Sign check for AragoDBPedia took 0.6064095497131348s
Availability | Check URIs Dereferenciability for AragoDBPedia took 3255.2230126857758s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 0.7879147529602051s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.020960092544555664s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for AragoDBPedia took 1.9073486328125e-06s
Believability | Calculation of trust value for AragoDBPedia took 6.67572021484375e-06s
INFO | --- Analysis for aragodbpedia took 11147.771700382233s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 30.444401502609253s
Availability | VoID file availability check for Archives Hub Linked Data took 0.0008511543273925781s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2642240524291992s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020734548568725586s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.507469177246094e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for archiveshub-linkeddata took 84.78359842300415s
Availability | SPARQL endpoint availability check for Archivi ISMA took 0.00011587142944335938s
Availability | VoID file availability check for Archivi ISMA took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.254427433013916s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.075599670410156e-05s
Believability | Calculation of trust value for Archivi ISMA took 8.344650268554688e-06s
INFO | --- Analysis for archivio-isma took 3.3856940269470215s
Availability | SPARQL endpoint availability check for ARIADNE took 4.124641418457031e-05s
Availability | VoID file availability check for ARIADNE took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2517421245574951s
Reputation | Calculation of the PageRank for ARIADNE took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for ARIADNE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.24249267578125e-05s
Believability | Calculation of trust value for ARIADNE took 7.62939453125e-06s
INFO | --- Analysis for ariadne took 2.921346664428711s
Availability | SPARQL endpoint availability check for Aristotle University took 8.296966552734375e-05s
Availability | VoID file availability check for Aristotle University took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2531013488769531s
Reputation | Calculation of the PageRank for Aristotle University took 0.021408796310424805s
Interlinking | Calculation of Degree of Connection for Aristotle University took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Aristotle University took 0.0008594989776611328s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.457069396972656e-05s
Believability | Calculation of trust value for Aristotle University took 8.106231689453125e-06s
INFO | --- Analysis for aristotle-university took 3.294320821762085s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 5.924333095550537s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.7172644138336182s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020616531372070312s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007870197296142578s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.2901763916015625e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 7.62939453125e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 21.51474356651306s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.315376281738281e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0003833770751953125s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.26962876319885254s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.24249267578125e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 7.867813110351562e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.876265048980713s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.8927576541900635s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2689971923828125s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.838539123535156e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 8.344650268554688e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 16.746423482894897s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.506111145019531e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006873607635498047s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.2524738311767578s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02037358283996582s
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.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00011014938354492188s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 5.9604644775390625e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 9.714597940444946s
Availability | SPARQL endpoint availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 4.220008850097656e-05s
Availability | VoID file availability check for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.2676124572753906s
Reputation | Calculation of the PageRank for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 1.2636184692382812e-05s
Believability | Calculation of trust value for Discourse on Articles (Sit'q'ua Art'ront'at'vis) took 7.867813110351562e-06s
INFO | --- Analysis for Arthron took 2.4168858528137207s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.482269287109375e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.2613036632537842s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02062535285949707s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 0.000102996826171875s
Believability | Calculation of trust value for Arthroscopy community took 8.106231689453125e-06s
INFO | --- Analysis for arthroscopy took 11.069832563400269s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 0.9490311145782471s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.0006759166717529297s
Extra | Recovery of all triples for Wikidata entry for Art × Science International took 21.487570762634277s
Performance | Total latancy measurement for Wikidata entry for Art × Science International took 1.123253583908081s
Amount of data | Number of triples check for Wikidata entry for Art × Science International took 65.16889953613281s
Interoperability | New terms check for Wikidata entry for Art × Science International took 2.002426862716675s
Versatility | Languages check for Wikidata entry for Art × Science International took 60.22152614593506s
Interpretability | Number of blank nodes check for Wikidata entry for Art × Science International took 65.18112587928772s
Interpretability | RDF structures check for Wikidata entry for Art × Science International took 0.46924901008605957s
Versatility | Serialization formats check for Wikidata entry for Art × Science International took 0.31081509590148926s
Availability | RDF dump link check for Wikidata entry for Art × Science International took 0.19613933563232422s
License | MR license check for Wikidata entry for Art × Science International took 0.2024383544921875s
License | HR license check for Wikidata entry for Art × Science International took 65.15993738174438s
Amount of data | Number of property check for Wikidata entry for Art × Science International took 0.3029322624206543s
Understandability | Number of label check for Wikidata entry for Art × Science International took 65.16415643692017s
Understandability | URI regex check for Wikidata entry for Art × Science International took 0.3689296245574951s
Understandability | Vocabs check for Wikidata entry for Art × Science International took 0.29992055892944336s
Verifiability | Authors check for Wikidata entry for Art × Science International took 0.186781644821167s
Verifiability | Publishers check for Wikidata entry for Art × Science International took 0.1867969036102295s
Amount of data | Check the number of entities for Wikidata entry for Art × Science International took 7.390975952148438e-05s
Verifiability | Contribs. check for Wikidata entry for Art × Science International took 0.1760725975036621s
Interlinking | sameAs chians check for Wikidata entry for Art × Science International took 16.585323333740234s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.17781901359558105s
Interlinking | skos check for Wikidata entry for Art × Science International took 0.18416476249694824s
Timeliness | dataset update frequency check for Wikidata entry for Art × Science International took 0.3054063320159912s
Currency | Creation date check for Wikidata entry for Art × Science International took 0.3637704849243164s
Currency | Modification date check for Wikidata entry for Art × Science International took 0.3863351345062256s
Rep.Conc. | URIs length for Wikidata entry for Art × Science International took 39.117271423339844s
Interoperability | New vocabularies check for Wikidata entry for Art × Science International took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Wikidata entry for Art × Science International took 0.19402194023132324s
Accuracy | Check Empty annotation labels for Wikidata entry for Art × Science International took 22.155404806137085s
Accuracy | Check White space in annotation for Wikidata entry for Art × Science International took 2.651871919631958s
Accuracy | Check Datatype consistency for Wikidata entry for Art × Science International took 4.52655553817749s
Consistency | Disjoint class check for Wikidata entry for Art × Science International took 0.1987161636352539s
Consistency | Check Misplaced properties for Wikidata entry for Art × Science International took 12.796842575073242s
Consistency | Misplaced classes for Wikidata entry for Art × Science International took 8.883917808532715s
Consistency | Check Ontology hijacking for Wikidata entry for Art × Science International took 30.70280694961548s
Consistency | Check Invalid usage of undefined classes for Wikidata entry for Art × Science International took 1.4404895305633545s
Consistency | Check Invalid usage of undefined properties for Wikidata entry for Art × Science International took 3.875875234603882s
Conciseness | Check Extensional conciseness for Wikidata entry for Art × Science International took 2.8312063217163086s
Conciseness | Check Intensional conciseness for Wikidata entry for Art × Science International took 1.6696760654449463s
Security | Sign check for Wikidata entry for Art × Science International took 0.3122406005859375s
Availability | Check URIs Dereferenciability for Wikidata entry for Art × Science International took 10.311370134353638s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.3812599182128906s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.33514404296875e-05s
Interoperability | Check the re-using of existing vocabs for Wikidata entry for Art × Science International took 1.430511474609375e-06s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 7.152557373046875e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 894.0387268066406s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.9784092903137207s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006155967712402344s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.26120686531066895s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.020679712295532227s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0007612705230712891s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 8.7738037109375e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.239776611328125e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 14.202787160873413s
Availability | SPARQL endpoint availability check for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 2.432396411895752s
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.0005781650543212891s
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.27695798873901367s
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.020479679107666016s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0007219314575195312s
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.796287536621094e-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 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 11.72376036643982s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.4413235187530518s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.28795576095581055s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 9.250640869140625e-05s
Believability | Calculation of trust value for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 12.789384603500366s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.4332242012023926s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0006034374237060547s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2848825454711914s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.020465850830078125s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.291534423828125e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-CRB took 14.883939504623413s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.419508218765259s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.679248571395874s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.083747863769531e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 6.198883056640625e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 12.621147632598877s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.4304919242858887s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.26980090141296387s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.020893096923828125s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.886222839355469e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-DQOT took 12.853843450546265s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.3955483436584473s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2631957530975342s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0207064151763916s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0009768009185791016s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.00010132789611816406s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.7404556274414062e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 12.91353702545166s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.4843156337738037s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0006349086761474609s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2701287269592285s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020770788192749023s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0010223388671875s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 9.417533874511719e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 9.298324584960938e-06s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 13.88595461845398s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.416246175765991s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0003561973571777344s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.24660706520080566s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.020261526107788086s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.173683166503906e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 12.17791748046875s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.42276668548584s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.259002685546875s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.7220458984375e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.152557373046875e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 12.124635219573975s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.150325536727905s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.27386951446533203s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.5299530029296875e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 17.504837036132812s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.413766860961914s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0005745887756347656s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2559797763824463s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.867813110351562e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 11.289818286895752s
Availability | SPARQL endpoint availability check for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 2.429311513900757s
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.0006031990051269531s
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.25465846061706543s
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.020545005798339844s
Interlinking | Calculation of Degree of Connection for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.987022399902344e-05s
Believability | Calculation of trust value for Dataset of the Chen Cheng-po’s Paintings and Documents (CCP) in the Taiwan Archive Information System (TAIS- ITH/ASCDC) at the Institute of Taiwan History, Academia Sinica took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 12.860097169876099s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.4071097373962402s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.25914502143859863s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 7.867813110351562e-06s
INFO | --- Analysis for ASCDC_-_DNB took 11.244700193405151s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 4.267692565917969e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.2578437328338623s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.021924495697021484s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 7.271766662597656e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 6.67572021484375e-06s
INFO | --- Analysis for asit took 8.074110984802246s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.3392181396484375e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.26414918899536133s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.020932912826538086s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0010216236114501953s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 4.482269287109375e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.62939453125e-06s
INFO | --- Analysis for asjp took 4.800388813018799s
Availability | SPARQL endpoint availability check for ASN:US took 0.09928488731384277s
Availability | VoID file availability check for ASN:US took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for ASN:US took 0.26850223541259766s
Reputation | Calculation of the PageRank for ASN:US took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for ASN:US took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.818771362304688e-05s
Believability | Calculation of trust value for ASN:US took 9.298324584960938e-06s
INFO | --- Analysis for asn-us took 6.297842502593994s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.315376281738281e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.26067566871643066s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.0517578125e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 4.76837158203125e-06s
INFO | --- Analysis for aspire-mmu took 4.423538684844971s
Availability | SPARQL endpoint availability check for associations took 4.2438507080078125e-05s
Availability | VoID file availability check for associations took 0.0006937980651855469s
Completeness | Calculation of interlinking completeness for associations took 0.286024808883667s
Reputation | Calculation of the PageRank for associations took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for associations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for associations took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for associations took 6.699562072753906e-05s
Believability | Calculation of trust value for associations took 7.867813110351562e-06s
INFO | --- Analysis for associations took 7.221790790557861s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.4345855712890625e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.24326133728027344s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 3.0040740966796875e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 7.62939453125e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.8633649349212646s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.2438507080078125e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0013346672058105469s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.2430589199066162s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020345211029052734s
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.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 9.036064147949219e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 7.3909759521484375e-06s
INFO | --- Analysis for athelia-rfid took 29.46784782409668s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.410743713378906e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2616090774536133s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.8764305114746094s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 0.6112196445465088s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2848188877105713s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020841598510742188s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 5.14984130859375e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for AugustiniConfessiones took 4.159249305725098s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 0.6372594833374023s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.2932698726654053s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02103900909423828s
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.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 9.775161743164062e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 7.152557373046875e-06s
INFO | --- Analysis for austrian_ski_racers took 3.876943826675415s
Availability | SPARQL endpoint availability check for AVsOnto took 4.410743713378906e-05s
Availability | VoID file availability check for AVsOnto took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.29260683059692383s
Reputation | Calculation of the PageRank for AVsOnto took 0.02059769630432129s
Interlinking | Calculation of Degree of Connection for AVsOnto took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.552436828613281e-05s
Believability | Calculation of trust value for AVsOnto took 5.9604644775390625e-06s
INFO | --- Analysis for AVsOnto took 3.2964742183685303s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.30632805824279785s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0005557537078857422s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 185.12361454963684s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5262138843536377s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0397381782532s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 198.397465467453s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10373640060425s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.06004190444946s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.23000407218933105s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.21369314193725586s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16942095756530762s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10263204574584961s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 49.40961670875549s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08684492111206s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13162899017333984s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 267.7657382488251s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2629079818725586s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.08669066429138184s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.11482763290405273s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09677958488464355s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.78187084197998s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.361701965332031e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10054349899291992s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.03943490982056s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.15435791015625s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10454511642456055s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12808966636657715s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2677445411682129s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.20534896850585938s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 585.2510550022125s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1501462459564209s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.686448097229004s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.2306325435638428s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.687977075576782s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1338212490081787s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.21787548065186s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 115.38139581680298s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.519484519958496s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.4235827922821s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.829385995864868s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1605536937713623s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.9313008785247803s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.2489726543426514s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021139144897460938s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.842613220214844e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.384185791015625e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.7220458984375e-06s
INFO | --- Analysis for b3kat took 4172.259200811386s
Availability | SPARQL endpoint availability check for BabelNet took 0.5582406520843506s
Availability | VoID file availability check for BabelNet took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for BabelNet took 0.26926326751708984s
Reputation | Calculation of the PageRank for BabelNet took 0.020678281784057617s
Interlinking | Calculation of Degree of Connection for BabelNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BabelNet took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.00016880035400390625s
Believability | Calculation of trust value for BabelNet took 8.106231689453125e-06s
INFO | --- Analysis for babelnet took 4.364291191101074s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 4.100799560546875e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.26785922050476074s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 3.075599670410156e-05s
Believability | Calculation of trust value for Bacevicius.lt took 6.67572021484375e-06s
INFO | --- Analysis for Bacevicius.lt took 2.692812204360962s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 0.5310807228088379s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2734806537628174s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.482269287109375e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 6.198883056640625e-06s
INFO | --- Analysis for bag took 4.856031894683838s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 7.007378339767456s
Availability | VoID file availability check for 红色经典歌曲 took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2681758403778076s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0008225440979003906s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.3855438232421875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue took 9.872984647750854s
Availability | SPARQL endpoint availability check for baixue composer took 5.459785461425781e-05s
Availability | VoID file availability check for baixue composer took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for baixue composer took 0.2661113739013672s
Reputation | Calculation of the PageRank for baixue composer took 0.02037835121154785s
Interlinking | Calculation of Degree of Connection for baixue composer took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for baixue composer took 0.0010325908660888672s
Interlinking | Calculation of Clustering coefficient for baixue composer took 3.7670135498046875e-05s
Believability | Calculation of trust value for baixue composer took 6.9141387939453125e-06s
INFO | --- Analysis for baixue_composer took 2.8290696144104004s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.3882598876953125e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006477832794189453s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2702479362487793s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02022409439086914s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.075599670410156e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.4373016357421875e-06s
INFO | --- Analysis for baixue_imagery took 2.947727918624878s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.38690185546875e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0006701946258544922s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.27652645111083984s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.123283386230469e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.152557373046875e-06s
INFO | --- Analysis for baixue_imagery1 took 3.6031830310821533s
Availability | SPARQL endpoint availability check for BAMS took 4.172325134277344e-05s
Availability | VoID file availability check for BAMS took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for BAMS took 0.24222421646118164s
Reputation | Calculation of the PageRank for BAMS took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for BAMS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for BAMS took 2.956390380859375e-05s
Believability | Calculation of trust value for BAMS took 7.3909759521484375e-06s
INFO | --- Analysis for bams took 2.9303064346313477s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.935264587402344e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.25865912437438965s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.021871328353881836s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.267692565917969e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.152557373046875e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.855513572692871s
Availability | SPARQL endpoint availability check for BBC Music took 0.3435366153717041s
Availability | VoID file availability check for BBC Music took 0.0007069110870361328s
Completeness | Calculation of interlinking completeness for BBC Music took 0.2716212272644043s
Reputation | Calculation of the PageRank for BBC Music took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for BBC Music took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BBC Music took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012803077697753906s
Believability | Calculation of trust value for BBC Music took 7.3909759521484375e-06s
INFO | --- Analysis for bbc-music took 3.2806437015533447s
Availability | SPARQL endpoint availability check for BBC Programmes took 0.23301911354064941s
Availability | VoID file availability check for BBC Programmes took 0.0006108283996582031s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.266420841217041s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 0.00010442733764648438s
Believability | Calculation of trust value for BBC Programmes took 7.152557373046875e-06s
INFO | --- Analysis for bbc-programmes took 10.693176746368408s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.253986120223999s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0007023811340332031s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.2444608211517334s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 0.00010228157043457031s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.198883056640625e-06s
INFO | --- Analysis for bbc-wildlife-finder took 9.471091985702515s
Availability | SPARQL endpoint availability check for BBOP took 4.1484832763671875e-05s
Availability | VoID file availability check for BBOP took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for BBOP took 0.2681589126586914s
Reputation | Calculation of the PageRank for BBOP took 0.028725385665893555s
Interlinking | Calculation of Degree of Connection for BBOP took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.814697265625e-05s
Believability | Calculation of trust value for BBOP took 8.58306884765625e-06s
INFO | --- Analysis for bbop took 2.9297335147857666s
Availability | SPARQL endpoint availability check for BBOP took 4.315376281738281e-05s
Availability | VoID file availability check for BBOP took 0.000873565673828125s
Completeness | Calculation of interlinking completeness for BBOP took 0.2559702396392822s
Reputation | Calculation of the PageRank for BBOP took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.7670135498046875e-05s
Believability | Calculation of trust value for BBOP took 6.67572021484375e-06s
INFO | --- Analysis for bbop-selected took 20.49939513206482s
Availability | SPARQL endpoint availability check for Bdgp took 1.7849326133728027s
Availability | VoID file availability check for Bdgp took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Bdgp took 0.2685065269470215s
Reputation | Calculation of the PageRank for Bdgp took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.218650817871094e-05s
Believability | Calculation of trust value for Bdgp took 7.62939453125e-06s
INFO | --- Analysis for bdgp took 8.577472686767578s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.363059997558594e-05s
Availability | VoID file availability check for Bendev Junior took 0.0012013912200927734s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.2559328079223633s
Reputation | Calculation of the PageRank for Bendev Junior took 0.021087169647216797s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.24249267578125e-05s
Believability | Calculation of trust value for Bendev Junior took 7.152557373046875e-06s
INFO | --- Analysis for bendevoficial took 7.094222545623779s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 3.9121575355529785s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.000675201416015625s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.272294282913208s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 7.343292236328125e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 5.7220458984375e-06s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 11.557917356491089s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.124641418457031e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.26870250701904297s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020876407623291016s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 3.314018249511719e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 6.67572021484375e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.938004732131958s
Availability | SPARQL endpoint availability check for berlios took 4.3392181396484375e-05s
Availability | VoID file availability check for berlios took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for berlios took 0.2690873146057129s
Reputation | Calculation of the PageRank for berlios took 0.020847082138061523s
Interlinking | Calculation of Degree of Connection for berlios took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for berlios took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for berlios took 9.608268737792969e-05s
Believability | Calculation of trust value for berlios took 7.62939453125e-06s
INFO | --- Analysis for berlios took 2.643784761428833s
Availability | SPARQL endpoint availability check for Between Our Worlds took 4.601478576660156e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.33319783210754395s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.021066904067993164s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 7.43865966796875e-05s
Believability | Calculation of trust value for Between Our Worlds took 6.67572021484375e-06s
INFO | --- Analysis for betweenourworlds took 9.262709617614746s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.4618098735809326s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.26581549644470215s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.942054748535156e-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 2.9670627117156982s
Availability | SPARQL endpoint availability check for BibBase took 0.09345865249633789s
Availability | VoID file availability check for BibBase took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for BibBase took 0.28087520599365234s
Reputation | Calculation of the PageRank for BibBase took 0.020613431930541992s
Interlinking | Calculation of Degree of Connection for BibBase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for BibBase took 9.775161743164062e-05s
Believability | Calculation of trust value for BibBase took 6.4373016357421875e-06s
INFO | --- Analysis for bibbase took 2.5032384395599365s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.678436279296875e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0009114742279052734s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.28316259384155273s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0009281635284423828s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00011086463928222656s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 7.152557373046875e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 8.386168241500854s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 5.817413330078125e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.27812981605529785s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.918212890625e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 9.5367431640625e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 8.343764066696167s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.696846008300781e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.28023552894592285s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0008265972137451172s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.24249267578125e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.9478936195373535s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 4.1961669921875e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006053447723388672s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.292203426361084s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.504753112792969e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 6.9141387939453125e-06s
INFO | --- Analysis for BibSonomy took 9.535961627960205s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.267692565917969e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.2691528797149658s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020197153091430664s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.8133392333984375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 6.9141387939453125e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 5.535108327865601s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.0006072521209716797s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.24404048919677734s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.0040740966796875e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.152557373046875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.6673367023468018s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 0.0006549358367919922s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.27518296241760254s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020418882369995117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.88900089263916s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 1.9151265621185303s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0005729198455810547s
Extra | Recovery of all triples for Bio2RDF::Affymetrix took 19.504069805145264s
Performance | Total latancy measurement for Bio2RDF::Affymetrix took 0.5035576820373535s
Amount of data | Number of triples check for Bio2RDF::Affymetrix took 45.854530334472656s
Interoperability | New terms check for Bio2RDF::Affymetrix took 42.856940031051636s
Versatility | Languages check for Bio2RDF::Affymetrix took 60.11633658409119s
Interpretability | Number of blank nodes check for Bio2RDF::Affymetrix took 0.15190505981445312s
Interpretability | RDF structures check for Bio2RDF::Affymetrix took 1.2716505527496338s
Versatility | Serialization formats check for Bio2RDF::Affymetrix took 0.27023911476135254s
Availability | RDF dump link check for Bio2RDF::Affymetrix took 6.218916177749634s
License | MR license check for Bio2RDF::Affymetrix took 0.37148571014404297s
License | HR license check for Bio2RDF::Affymetrix took 60.09599685668945s
Amount of data | Number of property check for Bio2RDF::Affymetrix took 0.1420612335205078s
Understandability | Number of label check for Bio2RDF::Affymetrix took 9.798569440841675s
Understandability | URI regex check for Bio2RDF::Affymetrix took 0.4074234962463379s
Understandability | Vocabs check for Bio2RDF::Affymetrix took 0.134598970413208s
Verifiability | Authors check for Bio2RDF::Affymetrix took 0.19063448905944824s
Verifiability | Publishers check for Bio2RDF::Affymetrix took 0.12859654426574707s
Performance | Throughput check for Bio2RDF::Affymetrix took 10.716676950454712s
Amount of data | Check the number of entities for Bio2RDF::Affymetrix took 72.34616494178772s
Verifiability | Contribs. check for Bio2RDF::Affymetrix took 0.741187334060669s
Interlinking | sameAs chians check for Bio2RDF::Affymetrix took 0.2380361557006836s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.9072086811065674s
Interlinking | skos check for Bio2RDF::Affymetrix took 0.20116972923278809s
Timeliness | dataset update frequency check for Bio2RDF::Affymetrix took 0.11801981925964355s
Currency | Creation date check for Bio2RDF::Affymetrix took 0.26441359519958496s
Currency | Modification date check for Bio2RDF::Affymetrix took 0.2439565658569336s
Rep.Conc. | URIs length for Bio2RDF::Affymetrix took 108.65996980667114s
Interoperability | New vocabularies check for Bio2RDF::Affymetrix took 28.902390956878662s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Affymetrix took 0.3251643180847168s
Accuracy | Check Functional Property for Bio2RDF::Affymetrix took 0.15802526473999023s
Accuracy | Check Inverse Functional Property for Bio2RDF::Affymetrix took 0.1268315315246582s
Accuracy | Check Empty annotation labels for Bio2RDF::Affymetrix took 7.685714960098267s
Accuracy | Check White space in annotation for Bio2RDF::Affymetrix took 0.8898909091949463s
Accuracy | Check Datatype consistency for Bio2RDF::Affymetrix took 0.6571595668792725s
Consistency | Disjoint class check for Bio2RDF::Affymetrix took 0.32086706161499023s
Consistency | Check Misplaced properties for Bio2RDF::Affymetrix took 64.84506630897522s
Consistency | Misplaced classes for Bio2RDF::Affymetrix took 2.24747371673584s
Consistency | Check Ontology hijacking for Bio2RDF::Affymetrix took 6.430263996124268s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Affymetrix took 1.2685775756835938s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Affymetrix took 61.39420127868652s
Conciseness | Check Extensional conciseness for Bio2RDF::Affymetrix took 0.714550256729126s
Conciseness | Check Intensional conciseness for Bio2RDF::Affymetrix took 0.3568241596221924s
Security | Sign check for Bio2RDF::Affymetrix took 0.1223299503326416s
Availability | Check URIs Dereferenciability for Bio2RDF::Affymetrix took 10.74272108078003s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.865821123123169s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 0.00010156631469726562s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Affymetrix took 27.76961398124695s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 2.0503997802734375e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 1060.1271395683289s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 0.5971639156341553s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.0006253719329833984s
Extra | Recovery of all triples for Bio2RDF::Biomodels took 18.701072692871094s
Performance | Total latancy measurement for Bio2RDF::Biomodels took 1.250091552734375s
Amount of data | Number of triples check for Bio2RDF::Biomodels took 44.18012261390686s
Interoperability | New terms check for Bio2RDF::Biomodels took 42.1653094291687s
Versatility | Languages check for Bio2RDF::Biomodels took 60.28503918647766s
Interpretability | Number of blank nodes check for Bio2RDF::Biomodels took 0.2799568176269531s
Security | Check HTTPS for Bio2RDF::Biomodels took 0.15635323524475098s
Interpretability | RDF structures check for Bio2RDF::Biomodels took 0.39038944244384766s
Versatility | Serialization formats check for Bio2RDF::Biomodels took 0.3113367557525635s
Availability | RDF dump link check for Bio2RDF::Biomodels took 6.374927520751953s
License | MR license check for Bio2RDF::Biomodels took 0.5039849281311035s
License | HR license check for Bio2RDF::Biomodels took 60.249298334121704s
Amount of data | Number of property check for Bio2RDF::Biomodels took 0.27397799491882324s
Understandability | Number of label check for Bio2RDF::Biomodels took 10.324565649032593s
Understandability | URI regex check for Bio2RDF::Biomodels took 0.5756134986877441s
Understandability | Vocabs check for Bio2RDF::Biomodels took 0.2682828903198242s
Verifiability | Authors check for Bio2RDF::Biomodels took 0.27599596977233887s
Verifiability | Publishers check for Bio2RDF::Biomodels took 0.2784600257873535s
Performance | Throughput check for Bio2RDF::Biomodels took 11.484461545944214s
Amount of data | Check the number of entities for Bio2RDF::Biomodels took 75.4743390083313s
Verifiability | Contribs. check for Bio2RDF::Biomodels took 0.6758184432983398s
Interlinking | sameAs chians check for Bio2RDF::Biomodels took 0.41901516914367676s
Interlinking | skos check for Bio2RDF::Biomodels took 0.9358241558074951s
Interlinking | skos check for Bio2RDF::Biomodels took 0.3569209575653076s
Timeliness | dataset update frequency check for Bio2RDF::Biomodels took 0.2617015838623047s
Currency | Creation date check for Bio2RDF::Biomodels took 0.5340149402618408s
Currency | Modification date check for Bio2RDF::Biomodels took 0.5165340900421143s
Rep.Conc. | URIs length for Bio2RDF::Biomodels took 109.19023275375366s
Interoperability | New vocabularies check for Bio2RDF::Biomodels took 66.00696778297424s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Biomodels took 0.42295265197753906s
Accuracy | Check Functional Property for Bio2RDF::Biomodels took 0.30333447456359863s
Accuracy | Check Inverse Functional Property for Bio2RDF::Biomodels took 0.2982020378112793s
Accuracy | Check Empty annotation labels for Bio2RDF::Biomodels took 7.446746826171875s
Accuracy | Check White space in annotation for Bio2RDF::Biomodels took 0.8934581279754639s
Accuracy | Check Datatype consistency for Bio2RDF::Biomodels took 0.6713669300079346s
Consistency | Disjoint class check for Bio2RDF::Biomodels took 0.4472167491912842s
Consistency | Check Misplaced properties for Bio2RDF::Biomodels took 65.16255521774292s
Consistency | Misplaced classes for Bio2RDF::Biomodels took 2.4473862648010254s
Consistency | Check Ontology hijacking for Bio2RDF::Biomodels took 6.433240652084351s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Biomodels took 1.2820041179656982s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Biomodels took 61.61612391471863s
Conciseness | Check Extensional conciseness for Bio2RDF::Biomodels took 0.699866771697998s
Conciseness | Check Intensional conciseness for Bio2RDF::Biomodels took 2.861928939819336s
Security | Sign check for Bio2RDF::Biomodels took 0.28954124450683594s
Availability | Check URIs Dereferenciability for Bio2RDF::Biomodels took 10.598473072052002s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 1.0128004550933838s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00011706352233886719s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Biomodels took 61.95802116394043s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels took 1144.2934873104095s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.5299530029296875e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.3011317253112793s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020877838134765625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.457069396972656e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 3.5438790321350098s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 0.5958802700042725s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005710124969482422s
Extra | Recovery of all triples for Bio2RDF::Bioportal took 20.601444959640503s
Performance | Total latancy measurement for Bio2RDF::Bioportal took 1.1916794776916504s
Amount of data | Number of triples check for Bio2RDF::Bioportal took 43.87308216094971s
Interoperability | New terms check for Bio2RDF::Bioportal took 40.77101278305054s
Versatility | Languages check for Bio2RDF::Bioportal took 60.23673963546753s
Interpretability | Number of blank nodes check for Bio2RDF::Bioportal took 0.2768692970275879s
Security | Check HTTPS for Bio2RDF::Bioportal took 0.15345382690429688s
Interpretability | RDF structures check for Bio2RDF::Bioportal took 0.5500524044036865s
Versatility | Serialization formats check for Bio2RDF::Bioportal took 0.33371543884277344s
Availability | RDF dump link check for Bio2RDF::Bioportal took 6.364095211029053s
License | MR license check for Bio2RDF::Bioportal took 0.5597357749938965s
License | HR license check for Bio2RDF::Bioportal took 60.2473726272583s
Amount of data | Number of property check for Bio2RDF::Bioportal took 0.2893044948577881s
Understandability | Number of label check for Bio2RDF::Bioportal took 10.053988218307495s
Understandability | URI regex check for Bio2RDF::Bioportal took 0.5561144351959229s
Understandability | Vocabs check for Bio2RDF::Bioportal took 0.25617551803588867s
Verifiability | Authors check for Bio2RDF::Bioportal took 0.26888561248779297s
Verifiability | Publishers check for Bio2RDF::Bioportal took 0.25854945182800293s
Performance | Throughput check for Bio2RDF::Bioportal took 10.87459659576416s
Amount of data | Check the number of entities for Bio2RDF::Bioportal took 73.30316257476807s
Verifiability | Contribs. check for Bio2RDF::Bioportal took 0.8364593982696533s
Interlinking | sameAs chians check for Bio2RDF::Bioportal took 0.3594064712524414s
Interlinking | skos check for Bio2RDF::Bioportal took 0.8577253818511963s
Interlinking | skos check for Bio2RDF::Bioportal took 0.37502312660217285s
Timeliness | dataset update frequency check for Bio2RDF::Bioportal took 0.26599764823913574s
Currency | Creation date check for Bio2RDF::Bioportal took 0.5035500526428223s
Currency | Modification date check for Bio2RDF::Bioportal took 0.5123651027679443s
Rep.Conc. | URIs length for Bio2RDF::Bioportal took 108.05842399597168s
Interoperability | New vocabularies check for Bio2RDF::Bioportal took 41.014278173446655s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Bioportal took 0.44338226318359375s
Accuracy | Check Functional Property for Bio2RDF::Bioportal took 0.294295072555542s
Accuracy | Check Inverse Functional Property for Bio2RDF::Bioportal took 0.2798502445220947s
Accuracy | Check Empty annotation labels for Bio2RDF::Bioportal took 7.710170269012451s
Accuracy | Check White space in annotation for Bio2RDF::Bioportal took 0.8882951736450195s
Accuracy | Check Datatype consistency for Bio2RDF::Bioportal took 0.6559352874755859s
Consistency | Disjoint class check for Bio2RDF::Bioportal took 0.4356203079223633s
Consistency | Check Misplaced properties for Bio2RDF::Bioportal took 65.19344568252563s
Consistency | Misplaced classes for Bio2RDF::Bioportal took 2.3831541538238525s
Consistency | Check Ontology hijacking for Bio2RDF::Bioportal took 6.133654594421387s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Bioportal took 1.315056562423706s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Bioportal took 61.54848861694336s
Conciseness | Check Extensional conciseness for Bio2RDF::Bioportal took 0.7054116725921631s
Conciseness | Check Intensional conciseness for Bio2RDF::Bioportal took 0.7039754390716553s
Security | Sign check for Bio2RDF::Bioportal took 0.291933536529541s
Availability | Check URIs Dereferenciability for Bio2RDF::Bioportal took 10.922306776046753s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.8916335105895996s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.024805068969726562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00041294097900390625s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Bioportal took 24.501315355300903s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 9.059906005859375e-06s
INFO | --- Analysis for bio2rdf-bioportal took 1086.7752003669739s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 0.14258575439453125s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0011851787567138672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.8264520168304443s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020076751708984375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.507469177246094e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-chembl took 18.315672397613525s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 0.5908632278442383s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0006072521209716797s
Extra | Recovery of all triples for Bio2RDF::Clinicaltrials took 19.3166241645813s
Performance | Total latancy measurement for Bio2RDF::Clinicaltrials took 1.199587345123291s
Amount of data | Number of triples check for Bio2RDF::Clinicaltrials took 43.41781282424927s
Interoperability | New terms check for Bio2RDF::Clinicaltrials took 40.89409399032593s
Versatility | Languages check for Bio2RDF::Clinicaltrials took 60.25220203399658s
Interpretability | Number of blank nodes check for Bio2RDF::Clinicaltrials took 0.2686913013458252s
Security | Check HTTPS for Bio2RDF::Clinicaltrials took 0.14553117752075195s
Interpretability | RDF structures check for Bio2RDF::Clinicaltrials took 0.796095609664917s
Versatility | Serialization formats check for Bio2RDF::Clinicaltrials took 0.31375741958618164s
Availability | RDF dump link check for Bio2RDF::Clinicaltrials took 6.415357351303101s
License | MR license check for Bio2RDF::Clinicaltrials took 0.5833079814910889s
License | HR license check for Bio2RDF::Clinicaltrials took 60.244152545928955s
Amount of data | Number of property check for Bio2RDF::Clinicaltrials took 0.2644622325897217s
Understandability | Number of label check for Bio2RDF::Clinicaltrials took 10.597767114639282s
Understandability | URI regex check for Bio2RDF::Clinicaltrials took 0.5557727813720703s
Understandability | Vocabs check for Bio2RDF::Clinicaltrials took 0.2678382396697998s
Verifiability | Authors check for Bio2RDF::Clinicaltrials took 0.2681257724761963s
Verifiability | Publishers check for Bio2RDF::Clinicaltrials took 0.25824594497680664s
Performance | Throughput check for Bio2RDF::Clinicaltrials took 11.224872827529907s
Amount of data | Check the number of entities for Bio2RDF::Clinicaltrials took 76.62004685401917s
Verifiability | Contribs. check for Bio2RDF::Clinicaltrials took 2.1763062477111816s
Interlinking | sameAs chians check for Bio2RDF::Clinicaltrials took 0.329134464263916s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.7241079807281494s
Interlinking | skos check for Bio2RDF::Clinicaltrials took 0.39034295082092285s
Timeliness | dataset update frequency check for Bio2RDF::Clinicaltrials took 0.29442286491394043s
Currency | Creation date check for Bio2RDF::Clinicaltrials took 0.5412197113037109s
Currency | Modification date check for Bio2RDF::Clinicaltrials took 0.5273494720458984s
Rep.Conc. | URIs length for Bio2RDF::Clinicaltrials took 114.46037173271179s
Interoperability | New vocabularies check for Bio2RDF::Clinicaltrials took 68.17427134513855s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Clinicaltrials took 0.41373515129089355s
Accuracy | Check Functional Property for Bio2RDF::Clinicaltrials took 0.2789640426635742s
Accuracy | Check Inverse Functional Property for Bio2RDF::Clinicaltrials took 0.2801327705383301s
Accuracy | Check Empty annotation labels for Bio2RDF::Clinicaltrials took 7.638913869857788s
Accuracy | Check White space in annotation for Bio2RDF::Clinicaltrials took 0.8846297264099121s
Accuracy | Check Datatype consistency for Bio2RDF::Clinicaltrials took 0.6834015846252441s
Consistency | Disjoint class check for Bio2RDF::Clinicaltrials took 0.45931053161621094s
Consistency | Check Misplaced properties for Bio2RDF::Clinicaltrials took 65.07230019569397s
Consistency | Misplaced classes for Bio2RDF::Clinicaltrials took 2.4103469848632812s
Consistency | Check Ontology hijacking for Bio2RDF::Clinicaltrials took 6.499178409576416s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Clinicaltrials took 1.337472915649414s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Clinicaltrials took 61.572551012039185s
Conciseness | Check Extensional conciseness for Bio2RDF::Clinicaltrials took 0.7097427845001221s
Conciseness | Check Intensional conciseness for Bio2RDF::Clinicaltrials took 0.7198524475097656s
Security | Sign check for Bio2RDF::Clinicaltrials took 0.27770495414733887s
Availability | Check URIs Dereferenciability for Bio2RDF::Clinicaltrials took 10.768871545791626s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.8792724609375s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.982948303222656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Clinicaltrials took 50.28563904762268s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1139.492885351181s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 0.5926661491394043s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0006232261657714844s
Extra | Recovery of all triples for Bio2RDF::Ctd took 18.494195222854614s
Performance | Total latancy measurement for Bio2RDF::Ctd took 1.1888163089752197s
Amount of data | Number of triples check for Bio2RDF::Ctd took 43.20683264732361s
Interoperability | New terms check for Bio2RDF::Ctd took 41.72092151641846s
Versatility | Languages check for Bio2RDF::Ctd took 60.24546718597412s
Interpretability | Number of blank nodes check for Bio2RDF::Ctd took 0.25930166244506836s
Security | Check HTTPS for Bio2RDF::Ctd took 0.1440112590789795s
Interpretability | RDF structures check for Bio2RDF::Ctd took 0.7625489234924316s
Versatility | Serialization formats check for Bio2RDF::Ctd took 0.3444709777832031s
Availability | RDF dump link check for Bio2RDF::Ctd took 6.344906330108643s
License | MR license check for Bio2RDF::Ctd took 0.5049772262573242s
License | HR license check for Bio2RDF::Ctd took 60.24721050262451s
Amount of data | Number of property check for Bio2RDF::Ctd took 0.3046565055847168s
Understandability | Number of label check for Bio2RDF::Ctd took 9.759345531463623s
Understandability | URI regex check for Bio2RDF::Ctd took 0.5858180522918701s
Understandability | Vocabs check for Bio2RDF::Ctd took 0.25059008598327637s
Verifiability | Authors check for Bio2RDF::Ctd took 0.26513051986694336s
Verifiability | Publishers check for Bio2RDF::Ctd took 0.2612903118133545s
Performance | Throughput check for Bio2RDF::Ctd took 11.437393188476562s
Amount of data | Check the number of entities for Bio2RDF::Ctd took 75.19373822212219s
Verifiability | Contribs. check for Bio2RDF::Ctd took 0.7068202495574951s
Interlinking | sameAs chians check for Bio2RDF::Ctd took 0.3568451404571533s
Interlinking | skos check for Bio2RDF::Ctd took 0.976306676864624s
Interlinking | skos check for Bio2RDF::Ctd took 0.3665127754211426s
Timeliness | dataset update frequency check for Bio2RDF::Ctd took 0.2636890411376953s
Currency | Creation date check for Bio2RDF::Ctd took 0.524630069732666s
Currency | Modification date check for Bio2RDF::Ctd took 0.5019001960754395s
Rep.Conc. | URIs length for Bio2RDF::Ctd took 112.7613308429718s
Interoperability | New vocabularies check for Bio2RDF::Ctd took 24.21210527420044s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ctd took 0.45290207862854004s
Accuracy | Check Functional Property for Bio2RDF::Ctd took 0.27543067932128906s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ctd took 0.2765839099884033s
Accuracy | Check Empty annotation labels for Bio2RDF::Ctd took 7.666528224945068s
Accuracy | Check White space in annotation for Bio2RDF::Ctd took 0.8937959671020508s
Accuracy | Check Datatype consistency for Bio2RDF::Ctd took 0.6873390674591064s
Consistency | Disjoint class check for Bio2RDF::Ctd took 0.4271869659423828s
Consistency | Check Misplaced properties for Bio2RDF::Ctd took 65.33813953399658s
Consistency | Misplaced classes for Bio2RDF::Ctd took 2.4232091903686523s
Consistency | Check Ontology hijacking for Bio2RDF::Ctd took 6.1096673011779785s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ctd took 1.3275656700134277s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ctd took 61.54478120803833s
Conciseness | Check Extensional conciseness for Bio2RDF::Ctd took 0.7034404277801514s
Conciseness | Check Intensional conciseness for Bio2RDF::Ctd took 0.43662548065185547s
Security | Sign check for Bio2RDF::Ctd took 0.27678394317626953s
Availability | Check URIs Dereferenciability for Bio2RDF::Ctd took 11.647186517715454s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.8824186325073242s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.031990051269531e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ctd took 21.2920823097229s
Believability | Calculation of trust value for Bio2RDF::Ctd took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-ctd took 1069.3373670578003s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 4.7206878662109375e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.676008939743042s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.863739013671875e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-dataset took 3.5128800868988037s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 0.6036298274993896s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.0005784034729003906s
Extra | Recovery of all triples for Bio2RDF::Dbsnp took 19.943755865097046s
Performance | Total latancy measurement for Bio2RDF::Dbsnp took 1.2656071186065674s
Amount of data | Number of triples check for Bio2RDF::Dbsnp took 44.1819429397583s
Interoperability | New terms check for Bio2RDF::Dbsnp took 42.97973680496216s
Versatility | Languages check for Bio2RDF::Dbsnp took 60.26849961280823s
Interpretability | Number of blank nodes check for Bio2RDF::Dbsnp took 0.3105194568634033s
Security | Check HTTPS for Bio2RDF::Dbsnp took 0.16716456413269043s
Interpretability | RDF structures check for Bio2RDF::Dbsnp took 0.9322700500488281s
Versatility | Serialization formats check for Bio2RDF::Dbsnp took 0.33759403228759766s
Availability | RDF dump link check for Bio2RDF::Dbsnp took 6.298526048660278s
License | MR license check for Bio2RDF::Dbsnp took 0.644439697265625s
License | HR license check for Bio2RDF::Dbsnp took 60.23831653594971s
Amount of data | Number of property check for Bio2RDF::Dbsnp took 0.2884640693664551s
Understandability | Number of label check for Bio2RDF::Dbsnp took 10.880245447158813s
Understandability | URI regex check for Bio2RDF::Dbsnp took 0.6064715385437012s
Understandability | Vocabs check for Bio2RDF::Dbsnp took 0.24227094650268555s
Verifiability | Authors check for Bio2RDF::Dbsnp took 0.2812206745147705s
Verifiability | Publishers check for Bio2RDF::Dbsnp took 0.2502889633178711s
Performance | Throughput check for Bio2RDF::Dbsnp took 11.52974557876587s
Amount of data | Check the number of entities for Bio2RDF::Dbsnp took 72.76182532310486s
Verifiability | Contribs. check for Bio2RDF::Dbsnp took 2.2807776927948s
Interlinking | sameAs chians check for Bio2RDF::Dbsnp took 0.3774547576904297s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.853656530380249s
Interlinking | skos check for Bio2RDF::Dbsnp took 0.35533976554870605s
Timeliness | dataset update frequency check for Bio2RDF::Dbsnp took 0.28879737854003906s
Currency | Creation date check for Bio2RDF::Dbsnp took 0.5536801815032959s
Currency | Modification date check for Bio2RDF::Dbsnp took 0.5347800254821777s
Rep.Conc. | URIs length for Bio2RDF::Dbsnp took 111.68172812461853s
Interoperability | New vocabularies check for Bio2RDF::Dbsnp took 30.869810342788696s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Dbsnp took 0.4736354351043701s
Accuracy | Check Functional Property for Bio2RDF::Dbsnp took 0.29903340339660645s
Accuracy | Check Inverse Functional Property for Bio2RDF::Dbsnp took 0.28416872024536133s
Accuracy | Check Empty annotation labels for Bio2RDF::Dbsnp took 7.1729795932769775s
Accuracy | Check White space in annotation for Bio2RDF::Dbsnp took 0.8978707790374756s
Accuracy | Check Datatype consistency for Bio2RDF::Dbsnp took 0.6602747440338135s
Consistency | Disjoint class check for Bio2RDF::Dbsnp took 0.5255787372589111s
Consistency | Check Misplaced properties for Bio2RDF::Dbsnp took 65.0763840675354s
Consistency | Misplaced classes for Bio2RDF::Dbsnp took 2.4087436199188232s
Consistency | Check Ontology hijacking for Bio2RDF::Dbsnp took 6.64416241645813s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Dbsnp took 1.3157668113708496s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Dbsnp took 61.55528450012207s
Conciseness | Check Extensional conciseness for Bio2RDF::Dbsnp took 0.7079470157623291s
Conciseness | Check Intensional conciseness for Bio2RDF::Dbsnp took 0.4088129997253418s
Security | Sign check for Bio2RDF::Dbsnp took 0.2838175296783447s
Availability | Check URIs Dereferenciability for Bio2RDF::Dbsnp took 11.5077965259552s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.5856976509094238s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.532669067382812e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Dbsnp took 23.403947114944458s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1072.6800122261047s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 0.5855000019073486s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0006990432739257812s
Extra | Recovery of all triples for Bio2RDF::Drugbank took 19.857282876968384s
Performance | Total latancy measurement for Bio2RDF::Drugbank took 1.2777886390686035s
Amount of data | Number of triples check for Bio2RDF::Drugbank took 43.85326385498047s
Interoperability | New terms check for Bio2RDF::Drugbank took 41.830923318862915s
Versatility | Languages check for Bio2RDF::Drugbank took 60.27813792228699s
Interpretability | Number of blank nodes check for Bio2RDF::Drugbank took 0.2747340202331543s
Security | Check HTTPS for Bio2RDF::Drugbank took 0.15449023246765137s
Interpretability | RDF structures check for Bio2RDF::Drugbank took 0.9975223541259766s
Versatility | Serialization formats check for Bio2RDF::Drugbank took 0.3210465908050537s
Availability | RDF dump link check for Bio2RDF::Drugbank took 6.700890302658081s
License | MR license check for Bio2RDF::Drugbank took 0.525054931640625s
License | HR license check for Bio2RDF::Drugbank took 60.249403953552246s
Amount of data | Number of property check for Bio2RDF::Drugbank took 0.27111077308654785s
Understandability | Number of label check for Bio2RDF::Drugbank took 10.427042961120605s
Understandability | URI regex check for Bio2RDF::Drugbank took 0.5571801662445068s
Understandability | Vocabs check for Bio2RDF::Drugbank took 0.24888896942138672s
Verifiability | Authors check for Bio2RDF::Drugbank took 0.266387939453125s
Verifiability | Publishers check for Bio2RDF::Drugbank took 0.24712419509887695s
Performance | Throughput check for Bio2RDF::Drugbank took 11.718831777572632s
Amount of data | Check the number of entities for Bio2RDF::Drugbank took 72.67304110527039s
Verifiability | Contribs. check for Bio2RDF::Drugbank took 0.6942086219787598s
Interlinking | sameAs chians check for Bio2RDF::Drugbank took 0.39760899543762207s
Interlinking | skos check for Bio2RDF::Drugbank took 0.993278980255127s
Interlinking | skos check for Bio2RDF::Drugbank took 0.39760494232177734s
Timeliness | dataset update frequency check for Bio2RDF::Drugbank took 0.2447037696838379s
Currency | Creation date check for Bio2RDF::Drugbank took 0.5117597579956055s
Currency | Modification date check for Bio2RDF::Drugbank took 0.5059168338775635s
Rep.Conc. | URIs length for Bio2RDF::Drugbank took 109.98243355751038s
Interoperability | New vocabularies check for Bio2RDF::Drugbank took 73.67463421821594s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Drugbank took 0.4460601806640625s
Accuracy | Check Functional Property for Bio2RDF::Drugbank took 0.27433347702026367s
Accuracy | Check Inverse Functional Property for Bio2RDF::Drugbank took 0.27977871894836426s
Accuracy | Check Empty annotation labels for Bio2RDF::Drugbank took 7.533179998397827s
Accuracy | Check White space in annotation for Bio2RDF::Drugbank took 0.8859407901763916s
Accuracy | Check Datatype consistency for Bio2RDF::Drugbank took 0.656071662902832s
Consistency | Disjoint class check for Bio2RDF::Drugbank took 0.42018771171569824s
Consistency | Check Misplaced properties for Bio2RDF::Drugbank took 65.62574529647827s
Consistency | Misplaced classes for Bio2RDF::Drugbank took 2.401066541671753s
Consistency | Check Ontology hijacking for Bio2RDF::Drugbank took 6.555410146713257s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Drugbank took 1.3122925758361816s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Drugbank took 61.509992599487305s
Conciseness | Check Extensional conciseness for Bio2RDF::Drugbank took 0.7013623714447021s
Conciseness | Check Intensional conciseness for Bio2RDF::Drugbank took 0.7172050476074219s
Security | Sign check for Bio2RDF::Drugbank took 0.2804715633392334s
Availability | Check URIs Dereferenciability for Bio2RDF::Drugbank took 13.970097303390503s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.6456122398376465s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.00010895729064941406s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Drugbank took 35.13669204711914s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-drugbank took 1130.8494834899902s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 0.5909755229949951s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0006654262542724609s
Extra | Recovery of all triples for Bio2RDF::Genage took 19.646496057510376s
Performance | Total latancy measurement for Bio2RDF::Genage took 1.224055528640747s
Amount of data | Number of triples check for Bio2RDF::Genage took 43.722755432128906s
Interoperability | New terms check for Bio2RDF::Genage took 41.60691475868225s
Versatility | Languages check for Bio2RDF::Genage took 60.247472047805786s
Interpretability | Number of blank nodes check for Bio2RDF::Genage took 0.2784419059753418s
Security | Check HTTPS for Bio2RDF::Genage took 0.15494298934936523s
Interpretability | RDF structures check for Bio2RDF::Genage took 0.7583715915679932s
Versatility | Serialization formats check for Bio2RDF::Genage took 0.32421064376831055s
Availability | RDF dump link check for Bio2RDF::Genage took 6.3103187084198s
License | MR license check for Bio2RDF::Genage took 0.48601698875427246s
License | HR license check for Bio2RDF::Genage took 60.241657733917236s
Amount of data | Number of property check for Bio2RDF::Genage took 0.3049435615539551s
Understandability | Number of label check for Bio2RDF::Genage took 10.226348161697388s
Understandability | URI regex check for Bio2RDF::Genage took 0.578615665435791s
Understandability | Vocabs check for Bio2RDF::Genage took 0.2682535648345947s
Verifiability | Authors check for Bio2RDF::Genage took 0.26740407943725586s
Verifiability | Publishers check for Bio2RDF::Genage took 0.2699394226074219s
Performance | Throughput check for Bio2RDF::Genage took 11.207602977752686s
Amount of data | Check the number of entities for Bio2RDF::Genage took 77.53483653068542s
Verifiability | Contribs. check for Bio2RDF::Genage took 2.9314284324645996s
Interlinking | sameAs chians check for Bio2RDF::Genage took 0.3809239864349365s
Interlinking | skos check for Bio2RDF::Genage took 0.9234724044799805s
Interlinking | skos check for Bio2RDF::Genage took 0.3496532440185547s
Timeliness | dataset update frequency check for Bio2RDF::Genage took 0.2522144317626953s
Currency | Creation date check for Bio2RDF::Genage took 0.5195596218109131s
Currency | Modification date check for Bio2RDF::Genage took 0.4946248531341553s
Rep.Conc. | URIs length for Bio2RDF::Genage took 110.41253590583801s
Interoperability | New vocabularies check for Bio2RDF::Genage took 21.816540956497192s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Genage took 0.4335780143737793s
Accuracy | Check Functional Property for Bio2RDF::Genage took 0.2683143615722656s
Accuracy | Check Inverse Functional Property for Bio2RDF::Genage took 0.2910940647125244s
Accuracy | Check Empty annotation labels for Bio2RDF::Genage took 7.601213693618774s
Accuracy | Check White space in annotation for Bio2RDF::Genage took 0.8955965042114258s
Accuracy | Check Datatype consistency for Bio2RDF::Genage took 0.6708672046661377s
Consistency | Disjoint class check for Bio2RDF::Genage took 0.4074976444244385s
Consistency | Check Misplaced properties for Bio2RDF::Genage took 65.40173149108887s
Consistency | Misplaced classes for Bio2RDF::Genage took 2.3627841472625732s
Consistency | Check Ontology hijacking for Bio2RDF::Genage took 6.345585107803345s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Genage took 1.3153283596038818s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Genage took 61.63379788398743s
Conciseness | Check Extensional conciseness for Bio2RDF::Genage took 0.7296555042266846s
Conciseness | Check Intensional conciseness for Bio2RDF::Genage took 0.4213235378265381s
Security | Sign check for Bio2RDF::Genage took 0.274444580078125s
Availability | Check URIs Dereferenciability for Bio2RDF::Genage took 11.796223163604736s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.9169943332672119s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.316734313964844e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Genage took 35.25843071937561s
Believability | Calculation of trust value for Bio2RDF::Genage took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-genage took 1078.9754662513733s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 5.53131103515625e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.7051489353179932s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 6.628036499023438e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-genbank took 5.56384801864624s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 0.5755701065063477s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0005712509155273438s
Extra | Recovery of all triples for Bio2RDF::Gendr took 20.737020015716553s
Performance | Total latancy measurement for Bio2RDF::Gendr took 1.2504451274871826s
Amount of data | Number of triples check for Bio2RDF::Gendr took 46.43138527870178s
Interoperability | New terms check for Bio2RDF::Gendr took 40.960124254226685s
Versatility | Languages check for Bio2RDF::Gendr took 60.28301191329956s
Interpretability | Number of blank nodes check for Bio2RDF::Gendr took 0.26796460151672363s
Security | Check HTTPS for Bio2RDF::Gendr took 0.16814589500427246s
Interpretability | RDF structures check for Bio2RDF::Gendr took 0.8757977485656738s
Versatility | Serialization formats check for Bio2RDF::Gendr took 0.2982773780822754s
Availability | RDF dump link check for Bio2RDF::Gendr took 6.282490015029907s
License | MR license check for Bio2RDF::Gendr took 0.4943997859954834s
License | HR license check for Bio2RDF::Gendr took 60.24387192726135s
Amount of data | Number of property check for Bio2RDF::Gendr took 0.2567405700683594s
Understandability | Number of label check for Bio2RDF::Gendr took 10.382337093353271s
Understandability | URI regex check for Bio2RDF::Gendr took 0.6147780418395996s
Understandability | Vocabs check for Bio2RDF::Gendr took 0.2565591335296631s
Verifiability | Authors check for Bio2RDF::Gendr took 0.2697713375091553s
Verifiability | Publishers check for Bio2RDF::Gendr took 0.2639327049255371s
Performance | Throughput check for Bio2RDF::Gendr took 10.401648759841919s
Amount of data | Check the number of entities for Bio2RDF::Gendr took 74.32729911804199s
Verifiability | Contribs. check for Bio2RDF::Gendr took 0.6823790073394775s
Interlinking | sameAs chians check for Bio2RDF::Gendr took 0.3817415237426758s
Interlinking | skos check for Bio2RDF::Gendr took 0.8760087490081787s
Interlinking | skos check for Bio2RDF::Gendr took 0.39931726455688477s
Timeliness | dataset update frequency check for Bio2RDF::Gendr took 0.2568931579589844s
Currency | Creation date check for Bio2RDF::Gendr took 0.49502134323120117s
Currency | Modification date check for Bio2RDF::Gendr took 0.5004308223724365s
Rep.Conc. | URIs length for Bio2RDF::Gendr took 110.14414167404175s
Interoperability | New vocabularies check for Bio2RDF::Gendr took 112.28215742111206s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Gendr took 0.42025089263916016s
Accuracy | Check Functional Property for Bio2RDF::Gendr took 0.2666194438934326s
Accuracy | Check Inverse Functional Property for Bio2RDF::Gendr took 0.273496150970459s
Accuracy | Check Empty annotation labels for Bio2RDF::Gendr took 7.224375247955322s
Accuracy | Check White space in annotation for Bio2RDF::Gendr took 0.8878810405731201s
Accuracy | Check Datatype consistency for Bio2RDF::Gendr took 0.6584005355834961s
Consistency | Disjoint class check for Bio2RDF::Gendr took 0.45502734184265137s
Consistency | Check Misplaced properties for Bio2RDF::Gendr took 65.15332078933716s
Consistency | Misplaced classes for Bio2RDF::Gendr took 2.7317214012145996s
Consistency | Check Ontology hijacking for Bio2RDF::Gendr took 6.73163366317749s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Gendr took 1.3420517444610596s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Gendr took 61.579633712768555s
Conciseness | Check Extensional conciseness for Bio2RDF::Gendr took 0.7174592018127441s
Conciseness | Check Intensional conciseness for Bio2RDF::Gendr took 0.43439579010009766s
Security | Sign check for Bio2RDF::Gendr took 0.2799530029296875s
Availability | Check URIs Dereferenciability for Bio2RDF::Gendr took 13.321420907974243s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.8861575126647949s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.02042412757873535s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.555152893066406e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Gendr took 62.7978949546814s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-gendr took 1197.4792337417603s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 0.5896368026733398s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0005457401275634766s
Extra | Recovery of all triples for Bio2RDF::Goa took 19.466023921966553s
Performance | Total latancy measurement for Bio2RDF::Goa took 1.2545719146728516s
Amount of data | Number of triples check for Bio2RDF::Goa took 43.510324239730835s
Interoperability | New terms check for Bio2RDF::Goa took 43.735191345214844s
Versatility | Languages check for Bio2RDF::Goa took 60.248305797576904s
Interpretability | Number of blank nodes check for Bio2RDF::Goa took 0.2996253967285156s
Security | Check HTTPS for Bio2RDF::Goa took 0.1558680534362793s
Interpretability | RDF structures check for Bio2RDF::Goa took 0.6815197467803955s
Versatility | Serialization formats check for Bio2RDF::Goa took 0.3334636688232422s
Availability | RDF dump link check for Bio2RDF::Goa took 6.371445417404175s
License | MR license check for Bio2RDF::Goa took 0.43405961990356445s
License | HR license check for Bio2RDF::Goa took 60.24748659133911s
Amount of data | Number of property check for Bio2RDF::Goa took 0.25917768478393555s
Understandability | Number of label check for Bio2RDF::Goa took 9.897932767868042s
Understandability | URI regex check for Bio2RDF::Goa took 0.5687718391418457s
Understandability | Vocabs check for Bio2RDF::Goa took 0.24886345863342285s
Verifiability | Authors check for Bio2RDF::Goa took 0.2720367908477783s
Verifiability | Publishers check for Bio2RDF::Goa took 0.2678985595703125s
Performance | Throughput check for Bio2RDF::Goa took 11.458425283432007s
Amount of data | Check the number of entities for Bio2RDF::Goa took 75.22068095207214s
Verifiability | Contribs. check for Bio2RDF::Goa took 2.1517157554626465s
Interlinking | sameAs chians check for Bio2RDF::Goa took 0.4015679359436035s
Interlinking | skos check for Bio2RDF::Goa took 1.0495336055755615s
Interlinking | skos check for Bio2RDF::Goa took 0.3682060241699219s
Timeliness | dataset update frequency check for Bio2RDF::Goa took 0.2715475559234619s
Currency | Creation date check for Bio2RDF::Goa took 0.4852287769317627s
Currency | Modification date check for Bio2RDF::Goa took 0.5221431255340576s
Rep.Conc. | URIs length for Bio2RDF::Goa took 109.2323830127716s
Interoperability | New vocabularies check for Bio2RDF::Goa took 78.5792932510376s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Goa took 0.44949984550476074s
Accuracy | Check Functional Property for Bio2RDF::Goa took 0.2727067470550537s
Accuracy | Check Inverse Functional Property for Bio2RDF::Goa took 0.27604246139526367s
Accuracy | Check Empty annotation labels for Bio2RDF::Goa took 7.279918909072876s
Accuracy | Check White space in annotation for Bio2RDF::Goa took 0.8871555328369141s
Accuracy | Check Datatype consistency for Bio2RDF::Goa took 0.6811976432800293s
Consistency | Disjoint class check for Bio2RDF::Goa took 0.39691686630249023s
Consistency | Check Misplaced properties for Bio2RDF::Goa took 65.41354727745056s
Consistency | Misplaced classes for Bio2RDF::Goa took 2.4686601161956787s
Consistency | Check Ontology hijacking for Bio2RDF::Goa took 6.308558702468872s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Goa took 1.3169441223144531s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Goa took 61.5146381855011s
Conciseness | Check Extensional conciseness for Bio2RDF::Goa took 0.6983652114868164s
Conciseness | Check Intensional conciseness for Bio2RDF::Goa took 0.6732206344604492s
Security | Sign check for Bio2RDF::Goa took 0.2773096561431885s
Availability | Check URIs Dereferenciability for Bio2RDF::Goa took 12.224958896636963s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.4866957664489746s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.151199340820312e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Goa took 94.15579557418823s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-goa took 1198.42129778862s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 0.5914294719696045s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0006415843963623047s
Extra | Recovery of all triples for Bio2RDF::Hgnc took 21.01423954963684s
Performance | Total latancy measurement for Bio2RDF::Hgnc took 1.2313158512115479s
Amount of data | Number of triples check for Bio2RDF::Hgnc took 43.29065728187561s
Interoperability | New terms check for Bio2RDF::Hgnc took 44.84632158279419s
Versatility | Languages check for Bio2RDF::Hgnc took 60.26558542251587s
Interpretability | Number of blank nodes check for Bio2RDF::Hgnc took 0.2679286003112793s
Security | Check HTTPS for Bio2RDF::Hgnc took 0.15476393699645996s
Interpretability | RDF structures check for Bio2RDF::Hgnc took 0.6997590065002441s
Versatility | Serialization formats check for Bio2RDF::Hgnc took 0.3175332546234131s
Availability | RDF dump link check for Bio2RDF::Hgnc took 6.349147796630859s
License | MR license check for Bio2RDF::Hgnc took 0.4678065776824951s
License | HR license check for Bio2RDF::Hgnc took 60.26675224304199s
Amount of data | Number of property check for Bio2RDF::Hgnc took 0.271925687789917s
Understandability | Number of label check for Bio2RDF::Hgnc took 9.665932893753052s
Understandability | URI regex check for Bio2RDF::Hgnc took 0.5643320083618164s
Understandability | Vocabs check for Bio2RDF::Hgnc took 0.24173760414123535s
Verifiability | Authors check for Bio2RDF::Hgnc took 0.2697432041168213s
Verifiability | Publishers check for Bio2RDF::Hgnc took 0.24830293655395508s
Performance | Throughput check for Bio2RDF::Hgnc took 11.471178531646729s
Amount of data | Check the number of entities for Bio2RDF::Hgnc took 76.2179868221283s
Verifiability | Contribs. check for Bio2RDF::Hgnc took 0.7380173206329346s
Interlinking | sameAs chians check for Bio2RDF::Hgnc took 0.38997602462768555s
Interlinking | skos check for Bio2RDF::Hgnc took 0.8811843395233154s
Interlinking | skos check for Bio2RDF::Hgnc took 0.35402512550354004s
Timeliness | dataset update frequency check for Bio2RDF::Hgnc took 0.27314186096191406s
Currency | Creation date check for Bio2RDF::Hgnc took 0.5003039836883545s
Currency | Modification date check for Bio2RDF::Hgnc took 0.506237268447876s
Rep.Conc. | URIs length for Bio2RDF::Hgnc took 109.84025645256042s
Interoperability | New vocabularies check for Bio2RDF::Hgnc took 94.03886818885803s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Hgnc took 0.42435193061828613s
Accuracy | Check Functional Property for Bio2RDF::Hgnc took 0.26128244400024414s
Accuracy | Check Inverse Functional Property for Bio2RDF::Hgnc took 0.27681541442871094s
Accuracy | Check Empty annotation labels for Bio2RDF::Hgnc took 7.066792249679565s
Accuracy | Check White space in annotation for Bio2RDF::Hgnc took 0.8981285095214844s
Accuracy | Check Datatype consistency for Bio2RDF::Hgnc took 0.664003849029541s
Consistency | Disjoint class check for Bio2RDF::Hgnc took 0.5137784481048584s
Consistency | Check Misplaced properties for Bio2RDF::Hgnc took 65.28953838348389s
Consistency | Misplaced classes for Bio2RDF::Hgnc took 2.421804189682007s
Consistency | Check Ontology hijacking for Bio2RDF::Hgnc took 6.036262273788452s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Hgnc took 1.2895009517669678s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Hgnc took 61.52682280540466s
Conciseness | Check Extensional conciseness for Bio2RDF::Hgnc took 0.7272956371307373s
Conciseness | Check Intensional conciseness for Bio2RDF::Hgnc took 0.7326827049255371s
Security | Sign check for Bio2RDF::Hgnc took 0.27361297607421875s
Availability | Check URIs Dereferenciability for Bio2RDF::Hgnc took 11.646652936935425s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 1.3271615505218506s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010585784912109375s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Hgnc took 68.62740778923035s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-hgnc took 1183.0519571304321s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 0.5772061347961426s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0006482601165771484s
Extra | Recovery of all triples for Bio2RDF::Homologene took 18.653021097183228s
Performance | Total latancy measurement for Bio2RDF::Homologene took 1.2649643421173096s
Amount of data | Number of triples check for Bio2RDF::Homologene took 44.402775049209595s
Interoperability | New terms check for Bio2RDF::Homologene took 42.372671604156494s
Versatility | Languages check for Bio2RDF::Homologene took 60.25087380409241s
Interpretability | Number of blank nodes check for Bio2RDF::Homologene took 0.26360583305358887s
Security | Check HTTPS for Bio2RDF::Homologene took 0.1571331024169922s
Interpretability | RDF structures check for Bio2RDF::Homologene took 0.7142632007598877s
Versatility | Serialization formats check for Bio2RDF::Homologene took 0.3269977569580078s
Availability | RDF dump link check for Bio2RDF::Homologene took 6.365349531173706s
License | MR license check for Bio2RDF::Homologene took 0.47159910202026367s
License | HR license check for Bio2RDF::Homologene took 60.25248622894287s
Amount of data | Number of property check for Bio2RDF::Homologene took 0.2875525951385498s
Understandability | Number of label check for Bio2RDF::Homologene took 10.325305223464966s
Understandability | URI regex check for Bio2RDF::Homologene took 0.6317479610443115s
Understandability | Vocabs check for Bio2RDF::Homologene took 0.25316429138183594s
Verifiability | Authors check for Bio2RDF::Homologene took 0.2830379009246826s
Verifiability | Publishers check for Bio2RDF::Homologene took 0.24308180809020996s
Performance | Throughput check for Bio2RDF::Homologene took 11.087328672409058s
Amount of data | Check the number of entities for Bio2RDF::Homologene took 72.69238901138306s
Verifiability | Contribs. check for Bio2RDF::Homologene took 0.8394436836242676s
Interlinking | sameAs chians check for Bio2RDF::Homologene took 0.35878944396972656s
Interlinking | skos check for Bio2RDF::Homologene took 0.8051962852478027s
Interlinking | skos check for Bio2RDF::Homologene took 0.3542959690093994s
Timeliness | dataset update frequency check for Bio2RDF::Homologene took 0.27112483978271484s
Currency | Creation date check for Bio2RDF::Homologene took 0.5090286731719971s
Currency | Modification date check for Bio2RDF::Homologene took 0.5124893188476562s
Rep.Conc. | URIs length for Bio2RDF::Homologene took 112.78943514823914s
Interoperability | New vocabularies check for Bio2RDF::Homologene took 42.85047268867493s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Homologene took 0.46915364265441895s
Accuracy | Check Functional Property for Bio2RDF::Homologene took 0.2751200199127197s
Accuracy | Check Inverse Functional Property for Bio2RDF::Homologene took 0.2889866828918457s
Accuracy | Check Empty annotation labels for Bio2RDF::Homologene took 7.59410834312439s
Accuracy | Check White space in annotation for Bio2RDF::Homologene took 0.8828926086425781s
Accuracy | Check Datatype consistency for Bio2RDF::Homologene took 0.6904885768890381s
Consistency | Disjoint class check for Bio2RDF::Homologene took 0.39021825790405273s
Consistency | Check Misplaced properties for Bio2RDF::Homologene took 65.26686811447144s
Consistency | Misplaced classes for Bio2RDF::Homologene took 2.3678972721099854s
Consistency | Check Ontology hijacking for Bio2RDF::Homologene took 6.385137319564819s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Homologene took 1.287872552871704s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Homologene took 61.65700054168701s
Conciseness | Check Extensional conciseness for Bio2RDF::Homologene took 0.7114827632904053s
Conciseness | Check Intensional conciseness for Bio2RDF::Homologene took 0.6727406978607178s
Security | Sign check for Bio2RDF::Homologene took 0.28458094596862793s
Availability | Check URIs Dereferenciability for Bio2RDF::Homologene took 12.199323415756226s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.5548715591430664s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.412101745605469e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Homologene took 104.80896472930908s
Believability | Calculation of trust value for Bio2RDF::Homologene took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-homologene took 1162.0339062213898s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 8.320808410644531e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.7106497287750244s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.02089548110961914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 1.3828277587890625e-05s
INFO | --- Analysis for bio2rdf-inoh took 5.496038913726807s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 0.581364631652832s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0005781650543212891s
Extra | Recovery of all triples for Bio2RDF::Interpro took 18.744378805160522s
Performance | Total latancy measurement for Bio2RDF::Interpro took 1.2739601135253906s
Amount of data | Number of triples check for Bio2RDF::Interpro took 44.19899010658264s
Interoperability | New terms check for Bio2RDF::Interpro took 42.19534683227539s
Versatility | Languages check for Bio2RDF::Interpro took 60.234612226486206s
Interpretability | Number of blank nodes check for Bio2RDF::Interpro took 0.2861964702606201s
Security | Check HTTPS for Bio2RDF::Interpro took 0.1473860740661621s
Interpretability | RDF structures check for Bio2RDF::Interpro took 0.848179817199707s
Versatility | Serialization formats check for Bio2RDF::Interpro took 0.29943132400512695s
Availability | RDF dump link check for Bio2RDF::Interpro took 6.314951658248901s
License | MR license check for Bio2RDF::Interpro took 0.4606907367706299s
License | HR license check for Bio2RDF::Interpro took 60.24893832206726s
Amount of data | Number of property check for Bio2RDF::Interpro took 0.2746589183807373s
Understandability | Number of label check for Bio2RDF::Interpro took 10.530866622924805s
Understandability | URI regex check for Bio2RDF::Interpro took 0.5785229206085205s
Understandability | Vocabs check for Bio2RDF::Interpro took 0.2648892402648926s
Verifiability | Authors check for Bio2RDF::Interpro took 0.26416587829589844s
Verifiability | Publishers check for Bio2RDF::Interpro took 0.2576253414154053s
Performance | Throughput check for Bio2RDF::Interpro took 11.50191354751587s
Amount of data | Check the number of entities for Bio2RDF::Interpro took 75.47658848762512s
Verifiability | Contribs. check for Bio2RDF::Interpro took 0.7200443744659424s
Interlinking | sameAs chians check for Bio2RDF::Interpro took 0.36084938049316406s
Interlinking | skos check for Bio2RDF::Interpro took 0.9273154735565186s
Interlinking | skos check for Bio2RDF::Interpro took 0.34228086471557617s
Timeliness | dataset update frequency check for Bio2RDF::Interpro took 0.2508406639099121s
Currency | Creation date check for Bio2RDF::Interpro took 0.5433404445648193s
Currency | Modification date check for Bio2RDF::Interpro took 0.5360143184661865s
Rep.Conc. | URIs length for Bio2RDF::Interpro took 110.61340236663818s
Interoperability | New vocabularies check for Bio2RDF::Interpro took 38.358213901519775s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Interpro took 0.4085268974304199s
Accuracy | Check Functional Property for Bio2RDF::Interpro took 0.2948768138885498s
Accuracy | Check Inverse Functional Property for Bio2RDF::Interpro took 0.2766602039337158s
Accuracy | Check Empty annotation labels for Bio2RDF::Interpro took 7.478355646133423s
Accuracy | Check White space in annotation for Bio2RDF::Interpro took 0.8892288208007812s
Accuracy | Check Datatype consistency for Bio2RDF::Interpro took 0.7010071277618408s
Consistency | Disjoint class check for Bio2RDF::Interpro took 0.39681506156921387s
Consistency | Check Misplaced properties for Bio2RDF::Interpro took 65.28402876853943s
Consistency | Misplaced classes for Bio2RDF::Interpro took 2.405916929244995s
Consistency | Check Ontology hijacking for Bio2RDF::Interpro took 6.9890031814575195s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Interpro took 1.2831296920776367s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Interpro took 61.52153825759888s
Conciseness | Check Extensional conciseness for Bio2RDF::Interpro took 0.700934886932373s
Conciseness | Check Intensional conciseness for Bio2RDF::Interpro took 2.3552496433258057s
Security | Sign check for Bio2RDF::Interpro took 0.2580277919769287s
Availability | Check URIs Dereferenciability for Bio2RDF::Interpro took 11.988812685012817s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 1.2611141204833984s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00011110305786132812s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Interpro took 45.61831045150757s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-interpro took 1105.5916936397552s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 0.13812041282653809s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0005996227264404297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.28320813179016113s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.020122528076171875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.295608520507812e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-iproclass took 18.4783673286438s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 0.5746779441833496s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0006649494171142578s
Extra | Recovery of all triples for Bio2RDF::Irefindex took 18.785715103149414s
Performance | Total latancy measurement for Bio2RDF::Irefindex took 1.2537071704864502s
Amount of data | Number of triples check for Bio2RDF::Irefindex took 43.420085430145264s
Interoperability | New terms check for Bio2RDF::Irefindex took 42.13526892662048s
Versatility | Languages check for Bio2RDF::Irefindex took 60.23735475540161s
Interpretability | Number of blank nodes check for Bio2RDF::Irefindex took 0.266284704208374s
Security | Check HTTPS for Bio2RDF::Irefindex took 0.16808271408081055s
Interpretability | RDF structures check for Bio2RDF::Irefindex took 0.8942248821258545s
Versatility | Serialization formats check for Bio2RDF::Irefindex took 0.34766173362731934s
Availability | RDF dump link check for Bio2RDF::Irefindex took 6.327866792678833s
License | MR license check for Bio2RDF::Irefindex took 0.48990535736083984s
License | HR license check for Bio2RDF::Irefindex took 60.25001621246338s
Amount of data | Number of property check for Bio2RDF::Irefindex took 0.3021876811981201s
Understandability | Number of label check for Bio2RDF::Irefindex took 10.109135627746582s
Understandability | URI regex check for Bio2RDF::Irefindex took 0.614408016204834s
Understandability | Vocabs check for Bio2RDF::Irefindex took 0.26241636276245117s
Verifiability | Authors check for Bio2RDF::Irefindex took 0.2505197525024414s
Verifiability | Publishers check for Bio2RDF::Irefindex took 0.2821812629699707s
Performance | Throughput check for Bio2RDF::Irefindex took 11.23487138748169s
Amount of data | Check the number of entities for Bio2RDF::Irefindex took 77.20700860023499s
Verifiability | Contribs. check for Bio2RDF::Irefindex took 0.8278439044952393s
Interlinking | sameAs chians check for Bio2RDF::Irefindex took 0.3779928684234619s
Interlinking | skos check for Bio2RDF::Irefindex took 0.9502317905426025s
Interlinking | skos check for Bio2RDF::Irefindex took 0.34395718574523926s
Timeliness | dataset update frequency check for Bio2RDF::Irefindex took 0.2610809803009033s
Currency | Creation date check for Bio2RDF::Irefindex took 0.5074801445007324s
Currency | Modification date check for Bio2RDF::Irefindex took 0.5453503131866455s
Rep.Conc. | URIs length for Bio2RDF::Irefindex took 108.93767166137695s
Interoperability | New vocabularies check for Bio2RDF::Irefindex took 65.98254656791687s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Irefindex took 0.47150492668151855s
Accuracy | Check Functional Property for Bio2RDF::Irefindex took 0.2620072364807129s
Accuracy | Check Inverse Functional Property for Bio2RDF::Irefindex took 0.2820596694946289s
Accuracy | Check Empty annotation labels for Bio2RDF::Irefindex took 7.13476300239563s
Accuracy | Check White space in annotation for Bio2RDF::Irefindex took 0.8805654048919678s
Accuracy | Check Datatype consistency for Bio2RDF::Irefindex took 0.6860809326171875s
Consistency | Disjoint class check for Bio2RDF::Irefindex took 0.47236061096191406s
Consistency | Check Misplaced properties for Bio2RDF::Irefindex took 65.22846984863281s
Consistency | Misplaced classes for Bio2RDF::Irefindex took 2.4053704738616943s
Consistency | Check Ontology hijacking for Bio2RDF::Irefindex took 6.112852334976196s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Irefindex took 1.2753493785858154s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Irefindex took 61.55920195579529s
Conciseness | Check Extensional conciseness for Bio2RDF::Irefindex took 0.7100141048431396s
Conciseness | Check Intensional conciseness for Bio2RDF::Irefindex took 0.7228801250457764s
Security | Sign check for Bio2RDF::Irefindex took 0.2707633972167969s
Availability | Check URIs Dereferenciability for Bio2RDF::Irefindex took 10.0338613986969s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 1.2336227893829346s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020828962326049805s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Irefindex took 97.43890500068665s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-irefindex took 1175.2782282829285s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.5299530029296875e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.2732408046722412s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.246566772460938e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-kegg took 3.391688585281372s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2634551525115967s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020518779754638672s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 4.255157470703125s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 0.14194083213806152s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0006504058837890625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.27097535133361816s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.0204617977142334s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 9.599971294403076s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 0.6011545658111572s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0005578994750976562s
Extra | Recovery of all triples for Bio2RDF::Lsr took 19.96250820159912s
Performance | Total latancy measurement for Bio2RDF::Lsr took 1.2948009967803955s
Amount of data | Number of triples check for Bio2RDF::Lsr took 44.130590200424194s
Interoperability | New terms check for Bio2RDF::Lsr took 43.340172290802s
Versatility | Languages check for Bio2RDF::Lsr took 60.22712063789368s
Interpretability | Number of blank nodes check for Bio2RDF::Lsr took 0.25722622871398926s
Security | Check HTTPS for Bio2RDF::Lsr took 0.16675662994384766s
Interpretability | RDF structures check for Bio2RDF::Lsr took 0.887718915939331s
Versatility | Serialization formats check for Bio2RDF::Lsr took 0.3128812313079834s
Availability | RDF dump link check for Bio2RDF::Lsr took 6.350377559661865s
License | MR license check for Bio2RDF::Lsr took 0.4882380962371826s
License | HR license check for Bio2RDF::Lsr took 60.25591278076172s
Amount of data | Number of property check for Bio2RDF::Lsr took 0.2707650661468506s
Understandability | Number of label check for Bio2RDF::Lsr took 10.273284673690796s
Understandability | URI regex check for Bio2RDF::Lsr took 0.5949516296386719s
Understandability | Vocabs check for Bio2RDF::Lsr took 0.27378344535827637s
Verifiability | Authors check for Bio2RDF::Lsr took 0.26723337173461914s
Verifiability | Publishers check for Bio2RDF::Lsr took 0.25629472732543945s
Performance | Throughput check for Bio2RDF::Lsr took 11.722385168075562s
Amount of data | Check the number of entities for Bio2RDF::Lsr took 74.16320657730103s
Verifiability | Contribs. check for Bio2RDF::Lsr took 3.1626882553100586s
Interlinking | sameAs chians check for Bio2RDF::Lsr took 0.3658277988433838s
Interlinking | skos check for Bio2RDF::Lsr took 0.7927455902099609s
Interlinking | skos check for Bio2RDF::Lsr took 0.33406662940979004s
Timeliness | dataset update frequency check for Bio2RDF::Lsr took 0.26609158515930176s
Currency | Creation date check for Bio2RDF::Lsr took 0.547605037689209s
Currency | Modification date check for Bio2RDF::Lsr took 0.5046167373657227s
Rep.Conc. | URIs length for Bio2RDF::Lsr took 111.381826877594s
Interoperability | New vocabularies check for Bio2RDF::Lsr took 81.05400443077087s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Lsr took 0.4460000991821289s
Accuracy | Check Functional Property for Bio2RDF::Lsr took 0.28929853439331055s
Accuracy | Check Inverse Functional Property for Bio2RDF::Lsr took 0.2654252052307129s
Accuracy | Check Empty annotation labels for Bio2RDF::Lsr took 7.111581563949585s
Accuracy | Check White space in annotation for Bio2RDF::Lsr took 0.8850281238555908s
Accuracy | Check Datatype consistency for Bio2RDF::Lsr took 0.693234920501709s
Consistency | Disjoint class check for Bio2RDF::Lsr took 0.39952659606933594s
Consistency | Check Misplaced properties for Bio2RDF::Lsr took 65.26116895675659s
Consistency | Misplaced classes for Bio2RDF::Lsr took 2.38323974609375s
Consistency | Check Ontology hijacking for Bio2RDF::Lsr took 7.121316432952881s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Lsr took 1.3216934204101562s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Lsr took 61.56458520889282s
Conciseness | Check Extensional conciseness for Bio2RDF::Lsr took 0.7157986164093018s
Conciseness | Check Intensional conciseness for Bio2RDF::Lsr took 0.7078580856323242s
Security | Sign check for Bio2RDF::Lsr took 0.2844080924987793s
Availability | Check URIs Dereferenciability for Bio2RDF::Lsr took 10.993988752365112s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 1.330796480178833s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02067112922668457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 5.125999450683594e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Lsr took 56.83680558204651s
Believability | Calculation of trust value for Bio2RDF::Lsr took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-lsr took 1160.55028963089s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 0.5844173431396484s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0006105899810791016s
Extra | Recovery of all triples for Bio2RDF::Mesh took 19.306775331497192s
Performance | Total latancy measurement for Bio2RDF::Mesh took 1.2397525310516357s
Amount of data | Number of triples check for Bio2RDF::Mesh took 44.3309600353241s
Interoperability | New terms check for Bio2RDF::Mesh took 44.3946099281311s
Versatility | Languages check for Bio2RDF::Mesh took 60.23330903053284s
Interpretability | Number of blank nodes check for Bio2RDF::Mesh took 0.26677680015563965s
Security | Check HTTPS for Bio2RDF::Mesh took 0.15600895881652832s
Interpretability | RDF structures check for Bio2RDF::Mesh took 0.8137743473052979s
Versatility | Serialization formats check for Bio2RDF::Mesh took 0.31658220291137695s
Availability | RDF dump link check for Bio2RDF::Mesh took 6.376511096954346s
License | MR license check for Bio2RDF::Mesh took 0.5309405326843262s
License | HR license check for Bio2RDF::Mesh took 60.249499797821045s
Amount of data | Number of property check for Bio2RDF::Mesh took 0.2891242504119873s
Understandability | Number of label check for Bio2RDF::Mesh took 10.961326599121094s
Understandability | URI regex check for Bio2RDF::Mesh took 0.5631189346313477s
Understandability | Vocabs check for Bio2RDF::Mesh took 0.25680994987487793s
Verifiability | Authors check for Bio2RDF::Mesh took 0.2709236145019531s
Verifiability | Publishers check for Bio2RDF::Mesh took 0.2503514289855957s
Performance | Throughput check for Bio2RDF::Mesh took 10.767604112625122s
Amount of data | Check the number of entities for Bio2RDF::Mesh took 76.69735360145569s
Verifiability | Contribs. check for Bio2RDF::Mesh took 0.6870043277740479s
Interlinking | sameAs chians check for Bio2RDF::Mesh took 0.35387492179870605s
Interlinking | skos check for Bio2RDF::Mesh took 0.903933048248291s
Interlinking | skos check for Bio2RDF::Mesh took 0.349348783493042s
Timeliness | dataset update frequency check for Bio2RDF::Mesh took 0.27254748344421387s
Currency | Creation date check for Bio2RDF::Mesh took 0.5164792537689209s
Currency | Modification date check for Bio2RDF::Mesh took 0.5083284378051758s
Rep.Conc. | URIs length for Bio2RDF::Mesh took 111.38471817970276s
Interoperability | New vocabularies check for Bio2RDF::Mesh took 59.39106845855713s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mesh took 0.46143031120300293s
Accuracy | Check Functional Property for Bio2RDF::Mesh took 0.28571605682373047s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mesh took 0.2874283790588379s
Accuracy | Check Empty annotation labels for Bio2RDF::Mesh took 7.364893436431885s
Accuracy | Check White space in annotation for Bio2RDF::Mesh took 0.8838284015655518s
Accuracy | Check Datatype consistency for Bio2RDF::Mesh took 0.6826090812683105s
Consistency | Disjoint class check for Bio2RDF::Mesh took 0.38674044609069824s
Consistency | Check Misplaced properties for Bio2RDF::Mesh took 65.6369833946228s
Consistency | Misplaced classes for Bio2RDF::Mesh took 2.416109323501587s
Consistency | Check Ontology hijacking for Bio2RDF::Mesh took 6.126877069473267s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mesh took 1.3293044567108154s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mesh took 61.52262234687805s
Conciseness | Check Extensional conciseness for Bio2RDF::Mesh took 0.7016053199768066s
Conciseness | Check Intensional conciseness for Bio2RDF::Mesh took 0.6720476150512695s
Security | Sign check for Bio2RDF::Mesh took 0.2813236713409424s
Availability | Check URIs Dereferenciability for Bio2RDF::Mesh took 11.078252077102661s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.6218059062957764s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.021020174026489258s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.891654968261719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mesh took 69.97037672996521s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-mesh took 1151.9469668865204s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 0.5961260795593262s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0006868839263916016s
Extra | Recovery of all triples for Bio2RDF::Mgi took 20.323031187057495s
Performance | Total latancy measurement for Bio2RDF::Mgi took 1.2863116264343262s
Amount of data | Number of triples check for Bio2RDF::Mgi took 45.02541995048523s
Interoperability | New terms check for Bio2RDF::Mgi took 42.23980784416199s
Versatility | Languages check for Bio2RDF::Mgi took 60.282010555267334s
Interpretability | Number of blank nodes check for Bio2RDF::Mgi took 0.2566061019897461s
Security | Check HTTPS for Bio2RDF::Mgi took 0.15634417533874512s
Interpretability | RDF structures check for Bio2RDF::Mgi took 0.5752639770507812s
Versatility | Serialization formats check for Bio2RDF::Mgi took 0.3528916835784912s
Availability | RDF dump link check for Bio2RDF::Mgi took 6.345118522644043s
License | MR license check for Bio2RDF::Mgi took 0.4727630615234375s
License | HR license check for Bio2RDF::Mgi took 60.25532603263855s
Amount of data | Number of property check for Bio2RDF::Mgi took 0.2736845016479492s
Understandability | Number of label check for Bio2RDF::Mgi took 10.244211673736572s
Understandability | URI regex check for Bio2RDF::Mgi took 0.5833389759063721s
Understandability | Vocabs check for Bio2RDF::Mgi took 0.24427103996276855s
Verifiability | Authors check for Bio2RDF::Mgi took 0.28662896156311035s
Verifiability | Publishers check for Bio2RDF::Mgi took 0.28375720977783203s
Performance | Throughput check for Bio2RDF::Mgi took 10.740297555923462s
Amount of data | Check the number of entities for Bio2RDF::Mgi took 76.18535780906677s
Verifiability | Contribs. check for Bio2RDF::Mgi took 2.9543299674987793s
Interlinking | sameAs chians check for Bio2RDF::Mgi took 0.3519744873046875s
Interlinking | skos check for Bio2RDF::Mgi took 0.886460542678833s
Interlinking | skos check for Bio2RDF::Mgi took 0.3520042896270752s
Timeliness | dataset update frequency check for Bio2RDF::Mgi took 0.2689030170440674s
Currency | Creation date check for Bio2RDF::Mgi took 0.49509191513061523s
Currency | Modification date check for Bio2RDF::Mgi took 0.48653268814086914s
Rep.Conc. | URIs length for Bio2RDF::Mgi took 111.10425400733948s
Interoperability | New vocabularies check for Bio2RDF::Mgi took 68.68426513671875s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Mgi took 0.4249885082244873s
Accuracy | Check Functional Property for Bio2RDF::Mgi took 0.2595248222351074s
Accuracy | Check Inverse Functional Property for Bio2RDF::Mgi took 0.2650721073150635s
Accuracy | Check Empty annotation labels for Bio2RDF::Mgi took 7.613979816436768s
Accuracy | Check White space in annotation for Bio2RDF::Mgi took 0.8853936195373535s
Accuracy | Check Datatype consistency for Bio2RDF::Mgi took 0.6905727386474609s
Consistency | Disjoint class check for Bio2RDF::Mgi took 0.41794800758361816s
Consistency | Check Misplaced properties for Bio2RDF::Mgi took 65.78087902069092s
Consistency | Misplaced classes for Bio2RDF::Mgi took 2.3738279342651367s
Consistency | Check Ontology hijacking for Bio2RDF::Mgi took 6.1822509765625s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Mgi took 1.3330752849578857s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Mgi took 61.514744997024536s
Conciseness | Check Extensional conciseness for Bio2RDF::Mgi took 0.716177225112915s
Conciseness | Check Intensional conciseness for Bio2RDF::Mgi took 1.4565258026123047s
Security | Sign check for Bio2RDF::Mgi took 0.2585904598236084s
Availability | Check URIs Dereferenciability for Bio2RDF::Mgi took 11.306813478469849s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.4943530559539795s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 8.893013000488281e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Mgi took 43.66999959945679s
Believability | Calculation of trust value for Bio2RDF::Mgi took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-mgi took 1139.4087126255035s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 0.5861294269561768s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0007104873657226562s
Extra | Recovery of all triples for Bio2RDF::Ncbigene took 18.40795373916626s
Performance | Total latancy measurement for Bio2RDF::Ncbigene took 1.2496745586395264s
Amount of data | Number of triples check for Bio2RDF::Ncbigene took 43.96333456039429s
Interoperability | New terms check for Bio2RDF::Ncbigene took 40.81184244155884s
Versatility | Languages check for Bio2RDF::Ncbigene took 60.250704526901245s
Interpretability | Number of blank nodes check for Bio2RDF::Ncbigene took 0.2743649482727051s
Security | Check HTTPS for Bio2RDF::Ncbigene took 0.15548491477966309s
Interpretability | RDF structures check for Bio2RDF::Ncbigene took 0.37996792793273926s
Versatility | Serialization formats check for Bio2RDF::Ncbigene took 0.3182704448699951s
Availability | RDF dump link check for Bio2RDF::Ncbigene took 6.309193134307861s
License | MR license check for Bio2RDF::Ncbigene took 0.43090176582336426s
License | HR license check for Bio2RDF::Ncbigene took 60.248040437698364s
Amount of data | Number of property check for Bio2RDF::Ncbigene took 0.2999122142791748s
Understandability | Number of label check for Bio2RDF::Ncbigene took 9.565225601196289s
Understandability | URI regex check for Bio2RDF::Ncbigene took 0.5977284908294678s
Understandability | Vocabs check for Bio2RDF::Ncbigene took 0.2775118350982666s
Verifiability | Authors check for Bio2RDF::Ncbigene took 0.27251338958740234s
Verifiability | Publishers check for Bio2RDF::Ncbigene took 0.2591264247894287s
Performance | Throughput check for Bio2RDF::Ncbigene took 11.755454540252686s
Amount of data | Check the number of entities for Bio2RDF::Ncbigene took 74.69093561172485s
Verifiability | Contribs. check for Bio2RDF::Ncbigene took 0.6587378978729248s
Interlinking | sameAs chians check for Bio2RDF::Ncbigene took 0.3599216938018799s
Interlinking | skos check for Bio2RDF::Ncbigene took 1.013453483581543s
Interlinking | skos check for Bio2RDF::Ncbigene took 0.4017624855041504s
Timeliness | dataset update frequency check for Bio2RDF::Ncbigene took 0.26511383056640625s
Currency | Creation date check for Bio2RDF::Ncbigene took 0.5024182796478271s
Currency | Modification date check for Bio2RDF::Ncbigene took 0.5164709091186523s
Rep.Conc. | URIs length for Bio2RDF::Ncbigene took 112.69034767150879s
Interoperability | New vocabularies check for Bio2RDF::Ncbigene took 79.00840425491333s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ncbigene took 0.45263147354125977s
Accuracy | Check Functional Property for Bio2RDF::Ncbigene took 0.2810940742492676s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ncbigene took 0.2826869487762451s
Accuracy | Check Empty annotation labels for Bio2RDF::Ncbigene took 7.3446431159973145s
Accuracy | Check White space in annotation for Bio2RDF::Ncbigene took 0.8850193023681641s
Accuracy | Check Datatype consistency for Bio2RDF::Ncbigene took 0.687675952911377s
Consistency | Disjoint class check for Bio2RDF::Ncbigene took 0.407820463180542s
Consistency | Check Misplaced properties for Bio2RDF::Ncbigene took 65.7943103313446s
Consistency | Misplaced classes for Bio2RDF::Ncbigene took 2.455559253692627s
Consistency | Check Ontology hijacking for Bio2RDF::Ncbigene took 6.398750066757202s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ncbigene took 1.2885494232177734s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ncbigene took 61.494157552719116s
Conciseness | Check Extensional conciseness for Bio2RDF::Ncbigene took 0.7064394950866699s
Conciseness | Check Intensional conciseness for Bio2RDF::Ncbigene took 0.6664376258850098s
Security | Sign check for Bio2RDF::Ncbigene took 0.27268171310424805s
Availability | Check URIs Dereferenciability for Bio2RDF::Ncbigene took 11.10709834098816s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.9364461898803711s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00012969970703125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ncbigene took 88.33039712905884s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 1187.1452798843384s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 0.5917589664459229s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.00031065940856933594s
Extra | Recovery of all triples for Bio2RDF::Ndc took 18.770843744277954s
Performance | Total latancy measurement for Bio2RDF::Ndc took 1.2641863822937012s
Amount of data | Number of triples check for Bio2RDF::Ndc took 46.31390690803528s
Interoperability | New terms check for Bio2RDF::Ndc took 40.790937185287476s
Versatility | Languages check for Bio2RDF::Ndc took 60.24124455451965s
Interpretability | Number of blank nodes check for Bio2RDF::Ndc took 0.280376672744751s
Security | Check HTTPS for Bio2RDF::Ndc took 0.14387774467468262s
Interpretability | RDF structures check for Bio2RDF::Ndc took 0.8192365169525146s
Versatility | Serialization formats check for Bio2RDF::Ndc took 0.32944631576538086s
Availability | RDF dump link check for Bio2RDF::Ndc took 6.363532304763794s
License | MR license check for Bio2RDF::Ndc took 0.48207831382751465s
License | HR license check for Bio2RDF::Ndc took 60.24477767944336s
Amount of data | Number of property check for Bio2RDF::Ndc took 0.2811582088470459s
Understandability | Number of label check for Bio2RDF::Ndc took 9.988808631896973s
Understandability | URI regex check for Bio2RDF::Ndc took 0.5957391262054443s
Understandability | Vocabs check for Bio2RDF::Ndc took 0.25342464447021484s
Verifiability | Authors check for Bio2RDF::Ndc took 0.2711646556854248s
Verifiability | Publishers check for Bio2RDF::Ndc took 0.2543661594390869s
Performance | Throughput check for Bio2RDF::Ndc took 11.49806261062622s
Amount of data | Check the number of entities for Bio2RDF::Ndc took 74.2469093799591s
Verifiability | Contribs. check for Bio2RDF::Ndc took 1.4683189392089844s
Interlinking | sameAs chians check for Bio2RDF::Ndc took 0.35660338401794434s
Interlinking | skos check for Bio2RDF::Ndc took 0.7404708862304688s
Interlinking | skos check for Bio2RDF::Ndc took 0.39573097229003906s
Timeliness | dataset update frequency check for Bio2RDF::Ndc took 0.2767355442047119s
Currency | Creation date check for Bio2RDF::Ndc took 0.4947223663330078s
Currency | Modification date check for Bio2RDF::Ndc took 0.5095615386962891s
Rep.Conc. | URIs length for Bio2RDF::Ndc took 111.20401000976562s
Interoperability | New vocabularies check for Bio2RDF::Ndc took 108.36719727516174s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Ndc took 0.4180915355682373s
Accuracy | Check Functional Property for Bio2RDF::Ndc took 0.2698178291320801s
Accuracy | Check Inverse Functional Property for Bio2RDF::Ndc took 0.2911651134490967s
Accuracy | Check Empty annotation labels for Bio2RDF::Ndc took 7.199666976928711s
Accuracy | Check White space in annotation for Bio2RDF::Ndc took 0.8937041759490967s
Accuracy | Check Datatype consistency for Bio2RDF::Ndc took 0.6671619415283203s
Consistency | Disjoint class check for Bio2RDF::Ndc took 0.417252779006958s
Consistency | Check Misplaced properties for Bio2RDF::Ndc took 65.48282527923584s
Consistency | Misplaced classes for Bio2RDF::Ndc took 2.446484088897705s
Consistency | Check Ontology hijacking for Bio2RDF::Ndc took 6.693025827407837s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Ndc took 1.294565200805664s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Ndc took 61.53283143043518s
Conciseness | Check Extensional conciseness for Bio2RDF::Ndc took 0.7253289222717285s
Conciseness | Check Intensional conciseness for Bio2RDF::Ndc took 0.40662431716918945s
Security | Sign check for Bio2RDF::Ndc took 0.26276350021362305s
Availability | Check URIs Dereferenciability for Bio2RDF::Ndc took 12.034165143966675s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.8590211868286133s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Ndc took 136.01579546928406s
Believability | Calculation of trust value for Bio2RDF::Ndc took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-ndc took 1263.625925540924s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.5299530029296875e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.27159881591796875s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.790855407714844e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-netpath took 4.748257160186768s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 0.13911032676696777s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0005772113800048828s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.254101037979126s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020206928253173828s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 5.9604644775390625e-06s
INFO | --- Analysis for bio2rdf-nextprot took 3.315397262573242s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 0.5801169872283936s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0006020069122314453s
Extra | Recovery of all triples for Bio2RDF::Omim took 21.74394702911377s
Performance | Total latancy measurement for Bio2RDF::Omim took 1.2412307262420654s
Amount of data | Number of triples check for Bio2RDF::Omim took 44.501734495162964s
Interoperability | New terms check for Bio2RDF::Omim took 41.21002769470215s
Versatility | Languages check for Bio2RDF::Omim took 60.276426553726196s
Interpretability | Number of blank nodes check for Bio2RDF::Omim took 0.26085400581359863s
Security | Check HTTPS for Bio2RDF::Omim took 0.14532685279846191s
Interpretability | RDF structures check for Bio2RDF::Omim took 0.8057997226715088s
Versatility | Serialization formats check for Bio2RDF::Omim took 0.33526015281677246s
Availability | RDF dump link check for Bio2RDF::Omim took 6.3594605922698975s
License | MR license check for Bio2RDF::Omim took 0.5747003555297852s
License | HR license check for Bio2RDF::Omim took 60.25060415267944s
Amount of data | Number of property check for Bio2RDF::Omim took 0.2778773307800293s
Understandability | Number of label check for Bio2RDF::Omim took 10.100078821182251s
Understandability | URI regex check for Bio2RDF::Omim took 0.6071922779083252s
Understandability | Vocabs check for Bio2RDF::Omim took 0.26633667945861816s
Verifiability | Authors check for Bio2RDF::Omim took 0.2656707763671875s
Verifiability | Publishers check for Bio2RDF::Omim took 0.2849431037902832s
Performance | Throughput check for Bio2RDF::Omim took 11.715903282165527s
Amount of data | Check the number of entities for Bio2RDF::Omim took 79.19230556488037s
Verifiability | Contribs. check for Bio2RDF::Omim took 0.7034518718719482s
Interlinking | sameAs chians check for Bio2RDF::Omim took 0.3334767818450928s
Interlinking | skos check for Bio2RDF::Omim took 0.7539136409759521s
Interlinking | skos check for Bio2RDF::Omim took 0.3591949939727783s
Timeliness | dataset update frequency check for Bio2RDF::Omim took 0.24666571617126465s
Currency | Creation date check for Bio2RDF::Omim took 0.5468394756317139s
Currency | Modification date check for Bio2RDF::Omim took 0.5307393074035645s
Rep.Conc. | URIs length for Bio2RDF::Omim took 108.36296105384827s
Interoperability | New vocabularies check for Bio2RDF::Omim took 107.6871817111969s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Omim took 0.4498171806335449s
Accuracy | Check Functional Property for Bio2RDF::Omim took 0.27627015113830566s
Accuracy | Check Inverse Functional Property for Bio2RDF::Omim took 0.2859363555908203s
Accuracy | Check Empty annotation labels for Bio2RDF::Omim took 6.7509472370147705s
Accuracy | Check White space in annotation for Bio2RDF::Omim took 0.8839845657348633s
Accuracy | Check Datatype consistency for Bio2RDF::Omim took 0.6715447902679443s
Consistency | Disjoint class check for Bio2RDF::Omim took 0.42577266693115234s
Consistency | Check Misplaced properties for Bio2RDF::Omim took 65.21708726882935s
Consistency | Misplaced classes for Bio2RDF::Omim took 2.405702590942383s
Consistency | Check Ontology hijacking for Bio2RDF::Omim took 6.11869740486145s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Omim took 1.296915054321289s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Omim took 61.83462977409363s
Conciseness | Check Extensional conciseness for Bio2RDF::Omim took 0.7051291465759277s
Conciseness | Check Intensional conciseness for Bio2RDF::Omim took 0.45403409004211426s
Security | Sign check for Bio2RDF::Omim took 0.29557323455810547s
Availability | Check URIs Dereferenciability for Bio2RDF::Omim took 11.091880798339844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 1.0365657806396484s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020726680755615234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00013327598571777344s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Omim took 70.45254230499268s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-omim took 1198.6166725158691s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.267692565917969e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0006744861602783203s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2564127445220947s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.220008850097656e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 2.7027175426483154s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 0.5760922431945801s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.0007061958312988281s
Extra | Recovery of all triples for Bio2RDF::Orphanet took 19.350849151611328s
Performance | Total latancy measurement for Bio2RDF::Orphanet took 1.2282037734985352s
Amount of data | Number of triples check for Bio2RDF::Orphanet took 43.9296772480011s
Interoperability | New terms check for Bio2RDF::Orphanet took 42.83044219017029s
Versatility | Languages check for Bio2RDF::Orphanet took 60.2530083656311s
Interpretability | Number of blank nodes check for Bio2RDF::Orphanet took 0.28407931327819824s
Security | Check HTTPS for Bio2RDF::Orphanet took 0.15567922592163086s
Interpretability | RDF structures check for Bio2RDF::Orphanet took 0.8846096992492676s
Versatility | Serialization formats check for Bio2RDF::Orphanet took 0.2969653606414795s
Availability | RDF dump link check for Bio2RDF::Orphanet took 6.406094789505005s
License | MR license check for Bio2RDF::Orphanet took 0.49157023429870605s
License | HR license check for Bio2RDF::Orphanet took 60.25632619857788s
Amount of data | Number of property check for Bio2RDF::Orphanet took 0.2707226276397705s
Understandability | Number of label check for Bio2RDF::Orphanet took 10.398694038391113s
Understandability | URI regex check for Bio2RDF::Orphanet took 0.5876312255859375s
Understandability | Vocabs check for Bio2RDF::Orphanet took 0.2561640739440918s
Verifiability | Authors check for Bio2RDF::Orphanet took 0.258394718170166s
Verifiability | Publishers check for Bio2RDF::Orphanet took 0.25893497467041016s
Performance | Throughput check for Bio2RDF::Orphanet took 11.444413900375366s
Amount of data | Check the number of entities for Bio2RDF::Orphanet took 74.20022583007812s
Verifiability | Contribs. check for Bio2RDF::Orphanet took 0.8324580192565918s
Interlinking | sameAs chians check for Bio2RDF::Orphanet took 0.3552863597869873s
Interlinking | skos check for Bio2RDF::Orphanet took 0.8549752235412598s
Interlinking | skos check for Bio2RDF::Orphanet took 0.37049293518066406s
Timeliness | dataset update frequency check for Bio2RDF::Orphanet took 0.27064990997314453s
Currency | Creation date check for Bio2RDF::Orphanet took 0.5499727725982666s
Currency | Modification date check for Bio2RDF::Orphanet took 0.533088207244873s
Rep.Conc. | URIs length for Bio2RDF::Orphanet took 110.98772740364075s
Interoperability | New vocabularies check for Bio2RDF::Orphanet took 37.19498372077942s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Orphanet took 0.4211153984069824s
Accuracy | Check Functional Property for Bio2RDF::Orphanet took 0.2702341079711914s
Accuracy | Check Inverse Functional Property for Bio2RDF::Orphanet took 0.2689516544342041s
Accuracy | Check Empty annotation labels for Bio2RDF::Orphanet took 7.5519492626190186s
Accuracy | Check White space in annotation for Bio2RDF::Orphanet took 0.8860759735107422s
Accuracy | Check Datatype consistency for Bio2RDF::Orphanet took 0.6570587158203125s
Consistency | Disjoint class check for Bio2RDF::Orphanet took 0.4578115940093994s
Consistency | Check Misplaced properties for Bio2RDF::Orphanet took 65.64872622489929s
Consistency | Misplaced classes for Bio2RDF::Orphanet took 2.4348297119140625s
Consistency | Check Ontology hijacking for Bio2RDF::Orphanet took 6.783196926116943s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Orphanet took 1.3418784141540527s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Orphanet took 61.528635025024414s
Conciseness | Check Extensional conciseness for Bio2RDF::Orphanet took 0.7041068077087402s
Conciseness | Check Intensional conciseness for Bio2RDF::Orphanet took 0.7238292694091797s
Security | Sign check for Bio2RDF::Orphanet took 0.27525925636291504s
Availability | Check URIs Dereferenciability for Bio2RDF::Orphanet took 12.464970111846924s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.4335446357727051s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.034706115722656e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Orphanet took 60.7168288230896s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1120.523294210434s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 0.14686322212219238s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.7021756172180176s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020087718963623047s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 10.824222087860107s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 0.5928466320037842s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.0006132125854492188s
Extra | Recovery of all triples for Bio2RDF::Pharmgkb took 19.486735343933105s
Performance | Total latancy measurement for Bio2RDF::Pharmgkb took 1.261631965637207s
Amount of data | Number of triples check for Bio2RDF::Pharmgkb took 43.58647704124451s
Interoperability | New terms check for Bio2RDF::Pharmgkb took 40.93089151382446s
Versatility | Languages check for Bio2RDF::Pharmgkb took 60.26399493217468s
Interpretability | Number of blank nodes check for Bio2RDF::Pharmgkb took 0.28612613677978516s
Security | Check HTTPS for Bio2RDF::Pharmgkb took 0.1559751033782959s
Interpretability | RDF structures check for Bio2RDF::Pharmgkb took 0.35114240646362305s
Versatility | Serialization formats check for Bio2RDF::Pharmgkb took 0.3248615264892578s
Availability | RDF dump link check for Bio2RDF::Pharmgkb took 6.4234209060668945s
License | MR license check for Bio2RDF::Pharmgkb took 0.44167399406433105s
License | HR license check for Bio2RDF::Pharmgkb took 60.267284870147705s
Amount of data | Number of property check for Bio2RDF::Pharmgkb took 0.25946998596191406s
Understandability | Number of label check for Bio2RDF::Pharmgkb took 10.3184974193573s
Understandability | URI regex check for Bio2RDF::Pharmgkb took 0.5699717998504639s
Understandability | Vocabs check for Bio2RDF::Pharmgkb took 0.24724793434143066s
Verifiability | Authors check for Bio2RDF::Pharmgkb took 0.2874469757080078s
Verifiability | Publishers check for Bio2RDF::Pharmgkb took 0.24474501609802246s
Performance | Throughput check for Bio2RDF::Pharmgkb took 11.02375602722168s
Amount of data | Check the number of entities for Bio2RDF::Pharmgkb took 73.91840887069702s
Verifiability | Contribs. check for Bio2RDF::Pharmgkb took 0.6749513149261475s
Interlinking | sameAs chians check for Bio2RDF::Pharmgkb took 0.3550393581390381s
Interlinking | skos check for Bio2RDF::Pharmgkb took 1.0329170227050781s
Interlinking | skos check for Bio2RDF::Pharmgkb took 0.3442721366882324s
Timeliness | dataset update frequency check for Bio2RDF::Pharmgkb took 0.2611355781555176s
Currency | Creation date check for Bio2RDF::Pharmgkb took 0.5426046848297119s
Currency | Modification date check for Bio2RDF::Pharmgkb took 0.5202691555023193s
Rep.Conc. | URIs length for Bio2RDF::Pharmgkb took 108.58720970153809s
Interoperability | New vocabularies check for Bio2RDF::Pharmgkb took 91.2136402130127s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pharmgkb took 0.4294157028198242s
Accuracy | Check Functional Property for Bio2RDF::Pharmgkb took 0.2804558277130127s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pharmgkb took 0.2642679214477539s
Accuracy | Check Empty annotation labels for Bio2RDF::Pharmgkb took 6.876614093780518s
Accuracy | Check White space in annotation for Bio2RDF::Pharmgkb took 0.8861935138702393s
Accuracy | Check Datatype consistency for Bio2RDF::Pharmgkb took 0.672562837600708s
Consistency | Disjoint class check for Bio2RDF::Pharmgkb took 0.408937931060791s
Consistency | Check Misplaced properties for Bio2RDF::Pharmgkb took 64.9403247833252s
Consistency | Misplaced classes for Bio2RDF::Pharmgkb took 2.4187569618225098s
Consistency | Check Ontology hijacking for Bio2RDF::Pharmgkb took 6.4837353229522705s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pharmgkb took 1.2845191955566406s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pharmgkb took 61.50021743774414s
Conciseness | Check Extensional conciseness for Bio2RDF::Pharmgkb took 0.7004079818725586s
Conciseness | Check Intensional conciseness for Bio2RDF::Pharmgkb took 2.3269731998443604s
Security | Sign check for Bio2RDF::Pharmgkb took 0.29176807403564453s
Availability | Check URIs Dereferenciability for Bio2RDF::Pharmgkb took 12.02669095993042s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.8977169990539551s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 7.891654968261719e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pharmgkb took 51.882086753845215s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 1157.3254897594452s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.76837158203125e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2821540832519531s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0009810924530029297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 4.0531158447265625e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 5.498231887817383s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0003116130828857422s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.7089848518371582s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0008220672607421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.218650817871094e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-pid took 3.4117727279663086s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0006897449493408203s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2577855587005615s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02008199691772461s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 2.86102294921875e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 3.7720224857330322s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 0.6203188896179199s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.0006918907165527344s
Extra | Recovery of all triples for Bio2RDF::Pubmed took 18.99860644340515s
Performance | Total latancy measurement for Bio2RDF::Pubmed took 1.2459614276885986s
Amount of data | Number of triples check for Bio2RDF::Pubmed took 44.28022074699402s
Interoperability | New terms check for Bio2RDF::Pubmed took 42.530441761016846s
Versatility | Languages check for Bio2RDF::Pubmed took 60.24432730674744s
Interpretability | Number of blank nodes check for Bio2RDF::Pubmed took 0.26718688011169434s
Security | Check HTTPS for Bio2RDF::Pubmed took 0.1683330535888672s
Interpretability | RDF structures check for Bio2RDF::Pubmed took 1.0713820457458496s
Versatility | Serialization formats check for Bio2RDF::Pubmed took 0.31931018829345703s
Availability | RDF dump link check for Bio2RDF::Pubmed took 6.420032262802124s
License | MR license check for Bio2RDF::Pubmed took 0.44629955291748047s
License | HR license check for Bio2RDF::Pubmed took 60.25591731071472s
Amount of data | Number of property check for Bio2RDF::Pubmed took 0.29551219940185547s
Understandability | Number of label check for Bio2RDF::Pubmed took 10.312439441680908s
Understandability | URI regex check for Bio2RDF::Pubmed took 0.5605342388153076s
Understandability | Vocabs check for Bio2RDF::Pubmed took 0.25714921951293945s
Verifiability | Authors check for Bio2RDF::Pubmed took 0.2816176414489746s
Verifiability | Publishers check for Bio2RDF::Pubmed took 0.2425999641418457s
Performance | Throughput check for Bio2RDF::Pubmed took 11.248804807662964s
Amount of data | Check the number of entities for Bio2RDF::Pubmed took 76.6473457813263s
Verifiability | Contribs. check for Bio2RDF::Pubmed took 0.8343818187713623s
Interlinking | sameAs chians check for Bio2RDF::Pubmed took 0.39320874214172363s
Interlinking | skos check for Bio2RDF::Pubmed took 0.8901753425598145s
Interlinking | skos check for Bio2RDF::Pubmed took 0.3455936908721924s
Timeliness | dataset update frequency check for Bio2RDF::Pubmed took 0.26801013946533203s
Currency | Creation date check for Bio2RDF::Pubmed took 0.5355186462402344s
Currency | Modification date check for Bio2RDF::Pubmed took 0.5187516212463379s
Rep.Conc. | URIs length for Bio2RDF::Pubmed took 109.27084875106812s
Interoperability | New vocabularies check for Bio2RDF::Pubmed took 66.55650877952576s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Pubmed took 0.4897193908691406s
Accuracy | Check Functional Property for Bio2RDF::Pubmed took 0.28116798400878906s
Accuracy | Check Inverse Functional Property for Bio2RDF::Pubmed took 0.28440308570861816s
Accuracy | Check Empty annotation labels for Bio2RDF::Pubmed took 7.015404224395752s
Accuracy | Check White space in annotation for Bio2RDF::Pubmed took 0.8895614147186279s
Accuracy | Check Datatype consistency for Bio2RDF::Pubmed took 0.6865458488464355s
Consistency | Disjoint class check for Bio2RDF::Pubmed took 0.41979432106018066s
Consistency | Check Misplaced properties for Bio2RDF::Pubmed took 65.04056668281555s
Consistency | Misplaced classes for Bio2RDF::Pubmed took 2.4200446605682373s
Consistency | Check Ontology hijacking for Bio2RDF::Pubmed took 6.285440444946289s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Pubmed took 1.332066535949707s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Pubmed took 61.52929878234863s
Conciseness | Check Extensional conciseness for Bio2RDF::Pubmed took 0.7123427391052246s
Conciseness | Check Intensional conciseness for Bio2RDF::Pubmed took 0.7319715023040771s
Security | Sign check for Bio2RDF::Pubmed took 0.27747511863708496s
Availability | Check URIs Dereferenciability for Bio2RDF::Pubmed took 12.306126594543457s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.8584718704223633s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.020890235900878906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00015878677368164062s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Pubmed took 103.83803081512451s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 1189.9850289821625s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 5.459785461425781e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.2644345760345459s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.02024698257446289s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.747245788574219e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-reactome took 3.8602793216705322s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 6.914138793945312e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.25097012519836426s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 7.128715515136719e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-rhea took 3.787297487258911s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 0.14878058433532715s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0003247261047363281s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.26630449295043945s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.295608520507812e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-sabiork took 9.328871011734009s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 0.5927047729492188s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0003261566162109375s
Extra | Recovery of all triples for Bio2RDF::Sgd took 18.9086651802063s
Performance | Total latancy measurement for Bio2RDF::Sgd took 1.195605754852295s
Amount of data | Number of triples check for Bio2RDF::Sgd took 43.73973894119263s
Interoperability | New terms check for Bio2RDF::Sgd took 41.813721656799316s
Versatility | Languages check for Bio2RDF::Sgd took 60.23596262931824s
Interpretability | Number of blank nodes check for Bio2RDF::Sgd took 0.27190160751342773s
Security | Check HTTPS for Bio2RDF::Sgd took 0.15651488304138184s
Interpretability | RDF structures check for Bio2RDF::Sgd took 0.728604793548584s
Versatility | Serialization formats check for Bio2RDF::Sgd took 0.3078954219818115s
Availability | RDF dump link check for Bio2RDF::Sgd took 6.414538621902466s
License | MR license check for Bio2RDF::Sgd took 0.4994666576385498s
License | HR license check for Bio2RDF::Sgd took 60.251986503601074s
Amount of data | Number of property check for Bio2RDF::Sgd took 0.27465200424194336s
Understandability | Number of label check for Bio2RDF::Sgd took 10.623460531234741s
Understandability | URI regex check for Bio2RDF::Sgd took 0.564183235168457s
Understandability | Vocabs check for Bio2RDF::Sgd took 0.23614215850830078s
Verifiability | Authors check for Bio2RDF::Sgd took 0.25035572052001953s
Verifiability | Publishers check for Bio2RDF::Sgd took 0.27056288719177246s
Performance | Throughput check for Bio2RDF::Sgd took 11.023414850234985s
Amount of data | Check the number of entities for Bio2RDF::Sgd took 74.01976251602173s
Verifiability | Contribs. check for Bio2RDF::Sgd took 2.9774725437164307s
Interlinking | sameAs chians check for Bio2RDF::Sgd took 0.37042856216430664s
Interlinking | skos check for Bio2RDF::Sgd took 0.9102356433868408s
Interlinking | skos check for Bio2RDF::Sgd took 0.3483850955963135s
Timeliness | dataset update frequency check for Bio2RDF::Sgd took 0.2686002254486084s
Currency | Creation date check for Bio2RDF::Sgd took 0.5311875343322754s
Currency | Modification date check for Bio2RDF::Sgd took 0.5122189521789551s
Rep.Conc. | URIs length for Bio2RDF::Sgd took 110.94830203056335s
Interoperability | New vocabularies check for Bio2RDF::Sgd took 100.25794458389282s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sgd took 0.44054675102233887s
Accuracy | Check Functional Property for Bio2RDF::Sgd took 0.2712745666503906s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sgd took 0.2872023582458496s
Accuracy | Check Empty annotation labels for Bio2RDF::Sgd took 6.891519069671631s
Accuracy | Check White space in annotation for Bio2RDF::Sgd took 0.8899986743927002s
Accuracy | Check Datatype consistency for Bio2RDF::Sgd took 0.6662030220031738s
Consistency | Disjoint class check for Bio2RDF::Sgd took 0.37654709815979004s
Consistency | Check Misplaced properties for Bio2RDF::Sgd took 64.96469402313232s
Consistency | Misplaced classes for Bio2RDF::Sgd took 2.384432077407837s
Consistency | Check Ontology hijacking for Bio2RDF::Sgd took 7.004992723464966s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sgd took 1.2873802185058594s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sgd took 61.768046617507935s
Conciseness | Check Extensional conciseness for Bio2RDF::Sgd took 0.700791597366333s
Conciseness | Check Intensional conciseness for Bio2RDF::Sgd took 0.4100942611694336s
Security | Sign check for Bio2RDF::Sgd took 0.28310489654541016s
Availability | Check URIs Dereferenciability for Bio2RDF::Sgd took 11.758254289627075s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 1.5239527225494385s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020804643630981445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00011157989501953125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sgd took 74.38221597671509s
Believability | Calculation of trust value for Bio2RDF::Sgd took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-sgd took 1190.5370469093323s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 9.369850158691406e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0006439685821533203s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.7508382797241211s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.504753112792969e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 4.694459438323975s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 0.5786890983581543s
Availability | VoID file availability check for Bio2RDF::Sider took 0.0005075931549072266s
Extra | Recovery of all triples for Bio2RDF::Sider took 19.0911967754364s
Performance | Total latancy measurement for Bio2RDF::Sider took 1.2453699111938477s
Amount of data | Number of triples check for Bio2RDF::Sider took 44.242703914642334s
Interoperability | New terms check for Bio2RDF::Sider took 41.06282663345337s
Versatility | Languages check for Bio2RDF::Sider took 60.25515532493591s
Interpretability | Number of blank nodes check for Bio2RDF::Sider took 0.31116271018981934s
Security | Check HTTPS for Bio2RDF::Sider took 0.14782428741455078s
Interpretability | RDF structures check for Bio2RDF::Sider took 0.4808933734893799s
Versatility | Serialization formats check for Bio2RDF::Sider took 0.3437061309814453s
Availability | RDF dump link check for Bio2RDF::Sider took 6.368187427520752s
License | MR license check for Bio2RDF::Sider took 0.5032088756561279s
License | HR license check for Bio2RDF::Sider took 60.23839998245239s
Amount of data | Number of property check for Bio2RDF::Sider took 0.25780272483825684s
Understandability | Number of label check for Bio2RDF::Sider took 10.743094682693481s
Understandability | URI regex check for Bio2RDF::Sider took 0.6093945503234863s
Understandability | Vocabs check for Bio2RDF::Sider took 0.2503983974456787s
Verifiability | Authors check for Bio2RDF::Sider took 0.2694098949432373s
Verifiability | Publishers check for Bio2RDF::Sider took 0.26867127418518066s
Performance | Throughput check for Bio2RDF::Sider took 11.07006025314331s
Amount of data | Check the number of entities for Bio2RDF::Sider took 75.09380578994751s
Verifiability | Contribs. check for Bio2RDF::Sider took 0.6862084865570068s
Interlinking | sameAs chians check for Bio2RDF::Sider took 0.4987330436706543s
Interlinking | skos check for Bio2RDF::Sider took 1.169675588607788s
Interlinking | skos check for Bio2RDF::Sider took 0.3331751823425293s
Timeliness | dataset update frequency check for Bio2RDF::Sider took 0.2666659355163574s
Currency | Creation date check for Bio2RDF::Sider took 0.5115289688110352s
Currency | Modification date check for Bio2RDF::Sider took 0.507831335067749s
Rep.Conc. | URIs length for Bio2RDF::Sider took 110.80491185188293s
Interoperability | New vocabularies check for Bio2RDF::Sider took 173.00683188438416s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Sider took 0.44761109352111816s
Accuracy | Check Functional Property for Bio2RDF::Sider took 0.2770113945007324s
Accuracy | Check Inverse Functional Property for Bio2RDF::Sider took 0.2555677890777588s
Accuracy | Check Empty annotation labels for Bio2RDF::Sider took 7.384769916534424s
Accuracy | Check White space in annotation for Bio2RDF::Sider took 0.8866758346557617s
Accuracy | Check Datatype consistency for Bio2RDF::Sider took 0.6712477207183838s
Consistency | Disjoint class check for Bio2RDF::Sider took 0.4288313388824463s
Consistency | Check Misplaced properties for Bio2RDF::Sider took 65.30986714363098s
Consistency | Misplaced classes for Bio2RDF::Sider took 2.377128839492798s
Consistency | Check Ontology hijacking for Bio2RDF::Sider took 5.98089337348938s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Sider took 1.281083583831787s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Sider took 61.5310697555542s
Conciseness | Check Extensional conciseness for Bio2RDF::Sider took 0.7123434543609619s
Conciseness | Check Intensional conciseness for Bio2RDF::Sider took 0.4204525947570801s
Security | Sign check for Bio2RDF::Sider took 0.2818927764892578s
Availability | Check URIs Dereferenciability for Bio2RDF::Sider took 12.49642539024353s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 1.2769434452056885s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.02034926414489746s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 4.315376281738281e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Sider took 99.8450973033905s
Believability | Calculation of trust value for Bio2RDF::Sider took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-sider took 1293.8271839618683s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.2638227939605713s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.02006077766418457s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-spike took 5.599104166030884s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 7.128715515136719e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0002982616424560547s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.28866076469421387s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.482269287109375e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 6.4373016357421875e-06s
INFO | --- Analysis for bio2rdf-taxon took 3.106952428817749s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 0.589439868927002s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0006892681121826172s
Extra | Recovery of all triples for Bio2RDF::Taxonomy took 18.62302827835083s
Performance | Total latancy measurement for Bio2RDF::Taxonomy took 1.3033027648925781s
Amount of data | Number of triples check for Bio2RDF::Taxonomy took 44.50183963775635s
Interoperability | New terms check for Bio2RDF::Taxonomy took 43.72028589248657s
Versatility | Languages check for Bio2RDF::Taxonomy took 60.255141258239746s
Interpretability | Number of blank nodes check for Bio2RDF::Taxonomy took 0.2528202533721924s
Security | Check HTTPS for Bio2RDF::Taxonomy took 0.16569805145263672s
Interpretability | RDF structures check for Bio2RDF::Taxonomy took 1.4112024307250977s
Versatility | Serialization formats check for Bio2RDF::Taxonomy took 0.3409538269042969s
Availability | RDF dump link check for Bio2RDF::Taxonomy took 6.290339469909668s
License | MR license check for Bio2RDF::Taxonomy took 0.4448995590209961s
License | HR license check for Bio2RDF::Taxonomy took 60.25809288024902s
Amount of data | Number of property check for Bio2RDF::Taxonomy took 0.25519514083862305s
Understandability | Number of label check for Bio2RDF::Taxonomy took 10.58236575126648s
Understandability | URI regex check for Bio2RDF::Taxonomy took 0.5766291618347168s
Understandability | Vocabs check for Bio2RDF::Taxonomy took 0.26360416412353516s
Verifiability | Authors check for Bio2RDF::Taxonomy took 0.26740503311157227s
Verifiability | Publishers check for Bio2RDF::Taxonomy took 0.23930573463439941s
Performance | Throughput check for Bio2RDF::Taxonomy took 11.493460655212402s
Amount of data | Check the number of entities for Bio2RDF::Taxonomy took 72.32113027572632s
Verifiability | Contribs. check for Bio2RDF::Taxonomy took 0.7224173545837402s
Interlinking | sameAs chians check for Bio2RDF::Taxonomy took 0.40821218490600586s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.9138903617858887s
Interlinking | skos check for Bio2RDF::Taxonomy took 0.35652661323547363s
Timeliness | dataset update frequency check for Bio2RDF::Taxonomy took 0.2533609867095947s
Currency | Creation date check for Bio2RDF::Taxonomy took 0.5104377269744873s
Currency | Modification date check for Bio2RDF::Taxonomy took 0.5163178443908691s
Rep.Conc. | URIs length for Bio2RDF::Taxonomy took 110.23855566978455s
Interoperability | New vocabularies check for Bio2RDF::Taxonomy took 20.852036476135254s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Taxonomy took 0.4528217315673828s
Accuracy | Check Functional Property for Bio2RDF::Taxonomy took 0.274747371673584s
Accuracy | Check Inverse Functional Property for Bio2RDF::Taxonomy took 0.23121356964111328s
Accuracy | Check Empty annotation labels for Bio2RDF::Taxonomy took 7.08304238319397s
Accuracy | Check White space in annotation for Bio2RDF::Taxonomy took 0.8822290897369385s
Accuracy | Check Datatype consistency for Bio2RDF::Taxonomy took 0.6608424186706543s
Consistency | Disjoint class check for Bio2RDF::Taxonomy took 0.40615296363830566s
Consistency | Check Misplaced properties for Bio2RDF::Taxonomy took 65.16340637207031s
Consistency | Misplaced classes for Bio2RDF::Taxonomy took 2.358049154281616s
Consistency | Check Ontology hijacking for Bio2RDF::Taxonomy took 6.37089204788208s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Taxonomy took 1.2824254035949707s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Taxonomy took 61.524290800094604s
Conciseness | Check Extensional conciseness for Bio2RDF::Taxonomy took 0.7016713619232178s
Conciseness | Check Intensional conciseness for Bio2RDF::Taxonomy took 0.40196871757507324s
Security | Sign check for Bio2RDF::Taxonomy took 0.25875091552734375s
Availability | Check URIs Dereferenciability for Bio2RDF::Taxonomy took 22.974804162979126s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.9944987297058105s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.0001220703125s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Taxonomy took 32.79450345039368s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1087.7228894233704s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 0.14566373825073242s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005602836608886719s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.698857307434082s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.024573326110839844s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.0040740966796875e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 8.821487426757812e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 18.590548276901245s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 0.5859382152557373s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.000614166259765625s
Extra | Recovery of all triples for Bio2RDF::Wormbase took 18.986493587493896s
Performance | Total latancy measurement for Bio2RDF::Wormbase took 1.214362382888794s
Amount of data | Number of triples check for Bio2RDF::Wormbase took 44.93510389328003s
Interoperability | New terms check for Bio2RDF::Wormbase took 40.95357537269592s
Versatility | Languages check for Bio2RDF::Wormbase took 60.22927951812744s
Interpretability | Number of blank nodes check for Bio2RDF::Wormbase took 0.28469300270080566s
Security | Check HTTPS for Bio2RDF::Wormbase took 0.15763258934020996s
Interpretability | RDF structures check for Bio2RDF::Wormbase took 0.8716633319854736s
Versatility | Serialization formats check for Bio2RDF::Wormbase took 0.3405282497406006s
Availability | RDF dump link check for Bio2RDF::Wormbase took 6.383770704269409s
License | MR license check for Bio2RDF::Wormbase took 0.4890177249908447s
License | HR license check for Bio2RDF::Wormbase took 60.260716676712036s
Amount of data | Number of property check for Bio2RDF::Wormbase took 0.26958537101745605s
Understandability | Number of label check for Bio2RDF::Wormbase took 9.760814666748047s
Understandability | URI regex check for Bio2RDF::Wormbase took 0.5985522270202637s
Understandability | Vocabs check for Bio2RDF::Wormbase took 0.2564582824707031s
Verifiability | Authors check for Bio2RDF::Wormbase took 0.29339599609375s
Verifiability | Publishers check for Bio2RDF::Wormbase took 0.26209354400634766s
Performance | Throughput check for Bio2RDF::Wormbase took 11.093594789505005s
Amount of data | Check the number of entities for Bio2RDF::Wormbase took 75.81277441978455s
Verifiability | Contribs. check for Bio2RDF::Wormbase took 0.7080173492431641s
Interlinking | sameAs chians check for Bio2RDF::Wormbase took 0.3574404716491699s
Interlinking | skos check for Bio2RDF::Wormbase took 0.7436914443969727s
Interlinking | skos check for Bio2RDF::Wormbase took 0.3434336185455322s
Timeliness | dataset update frequency check for Bio2RDF::Wormbase took 0.2695152759552002s
Currency | Creation date check for Bio2RDF::Wormbase took 0.5315344333648682s
Currency | Modification date check for Bio2RDF::Wormbase took 0.527277946472168s
Rep.Conc. | URIs length for Bio2RDF::Wormbase took 107.74355840682983s
Interoperability | New vocabularies check for Bio2RDF::Wormbase took 69.69677519798279s
Consistency | Deprecated classes/propertiers check for Bio2RDF::Wormbase took 0.4436509609222412s
Accuracy | Check Functional Property for Bio2RDF::Wormbase took 0.27906036376953125s
Accuracy | Check Inverse Functional Property for Bio2RDF::Wormbase took 0.2918698787689209s
Accuracy | Check Empty annotation labels for Bio2RDF::Wormbase took 7.057673931121826s
Accuracy | Check White space in annotation for Bio2RDF::Wormbase took 0.8884263038635254s
Accuracy | Check Datatype consistency for Bio2RDF::Wormbase took 0.676682710647583s
Consistency | Disjoint class check for Bio2RDF::Wormbase took 0.37330031394958496s
Consistency | Check Misplaced properties for Bio2RDF::Wormbase took 64.92122507095337s
Consistency | Misplaced classes for Bio2RDF::Wormbase took 2.4307634830474854s
Consistency | Check Ontology hijacking for Bio2RDF::Wormbase took 6.088729619979858s
Consistency | Check Invalid usage of undefined classes for Bio2RDF::Wormbase took 1.2739357948303223s
Consistency | Check Invalid usage of undefined properties for Bio2RDF::Wormbase took 61.52298641204834s
Conciseness | Check Extensional conciseness for Bio2RDF::Wormbase took 0.7136256694793701s
Conciseness | Check Intensional conciseness for Bio2RDF::Wormbase took 0.7889196872711182s
Security | Sign check for Bio2RDF::Wormbase took 0.27322983741760254s
Availability | Check URIs Dereferenciability for Bio2RDF::Wormbase took 27.994215488433838s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.36511898040771484s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.724761962890625e-05s
Interoperability | Check the re-using of existing vocabs for Bio2RDF::Wormbase took 50.48558068275452s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-wormbase took 1159.8693099021912s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 4.57763671875e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.28773999214172363s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020188331604003906s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.239776611328125e-05s
Believability | Calculation of trust value for Biografías y Vidas took 6.67572021484375e-06s
INFO | --- Analysis for biografiasyvidas took 3.661296844482422s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 0.24619197845458984s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.6963586807250977s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0008511543273925781s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 0.00010132789611816406s
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 4.402534008026123s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0001239776611328125s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.26431846618652344s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.8371810913085938e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for biolit took 3.3043999671936035s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 6.818771362304688e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.28153038024902344s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.021371841430664062s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0009512901306152344s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 4.7206878662109375e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 6.4373016357421875e-06s
INFO | --- Analysis for biolod-pdb took 8.520573616027832s
Availability | SPARQL endpoint availability check for BioModels RDF took 0.6277704238891602s
Availability | VoID file availability check for BioModels RDF took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.27636075019836426s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020322561264038086s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for BioModels RDF took 5.4836273193359375e-06s
INFO | --- Analysis for biomodels-rdf took 3.7309882640838623s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.7652502059936523s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.26799631118774414s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.67572021484375e-06s
INFO | --- Analysis for Biop took 8.465749740600586s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.3392181396484375e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.25946807861328125s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.504753112792969e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 7.3909759521484375e-06s
INFO | --- Analysis for Bioportal took 2.4971983432769775s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.38690185546875e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.3018803596496582s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006527900695800781s
Believability | Calculation of trust value for Amphibian gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-aao took 2.8658664226531982s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.267692565917969e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2576112747192383s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0008041858673095703s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0003070831298828125s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-aba took 2.7106151580810547s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0005028247833251953s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.2401723861694336s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.020997285842895508s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0015208721160888672s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-acgt took 2.6457700729370117s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 4.315376281738281e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2837960720062256s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003418922424316406s
Believability | Calculation of trust value for Animal natural history and life history took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-adw took 2.7860820293426514s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.27556276321411133s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02019023895263672s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.00047135353088378906s
Believability | Calculation of trust value for Anatomical Entity Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-aeo took 2.7289276123046875s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.26905393600463867s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009613037109375s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-aero took 2.632584571838379s
Availability | SPARQL endpoint availability check for AI/RHEUM took 4.2438507080078125e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.2926056385040283s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003902912139892578s
Believability | Calculation of trust value for AI/RHEUM took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-air took 2.823974847793579s
Availability | SPARQL endpoint availability check for Amino Acid took 4.2438507080078125e-05s
Availability | VoID file availability check for Amino Acid took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.27393293380737305s
Reputation | Calculation of the PageRank for Amino Acid took 0.02082228660583496s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0009253025054931641s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0003046989440917969s
Believability | Calculation of trust value for Amino Acid took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.690232276916504s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0005106925964355469s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.263552188873291s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020444869995117188s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002865791320800781s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-apo took 2.6017508506774902s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 8.177757263183594e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.26734423637390137s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00024199485778808594s
Believability | Calculation of trust value for African Traditional Medicine took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-atmo took 2.6280791759490967s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.863739013671875e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2668023109436035s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.845329284667969e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ato took 2.617083787918091s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.2462620735168457s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020764827728271484s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0013687610626220703s
Believability | Calculation of trust value for BioAssay Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bao took 2.569941759109497s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2542903423309326s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.02055978775024414s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00038695335388183594s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.611917495727539s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2793712615966797s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020223379135131836s
Interlinking | Calculation of Degree of Connection for Breast Cancer Grading Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Breast Cancer Grading Ontology took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.00032520294189453125s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bcgo took 2.6490774154663086s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.27200865745544434s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.02032160758972168s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014023780822753906s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-bdo took 2.633345365524292s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.28041768074035645s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004928112030029297s
Believability | Calculation of trust value for Basic Formal Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bfo took 2.65692138671875s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.38690185546875e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005285739898681641s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.2539982795715332s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007336139678955078s
Believability | Calculation of trust value for Bleeding History Phenotype took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bho took 2.6439926624298096s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.458427429199219e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.29215002059936523s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00046324729919433594s
Believability | Calculation of trust value for Bilateria anatomy took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bila took 2.723483085632324s
Availability | SPARQL endpoint availability check for BIRNLex took 4.267692565917969e-05s
Availability | VoID file availability check for BIRNLex took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.2594332695007324s
Reputation | Calculation of the PageRank for BIRNLex took 0.021283626556396484s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.001146554946899414s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0017540454864501953s
Believability | Calculation of trust value for BIRNLex took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-birnlex took 2.569016695022583s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2806859016418457s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007212162017822266s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.6360180377960205s
Availability | SPARQL endpoint availability check for BioPAX took 4.267692565917969e-05s
Availability | VoID file availability check for BioPAX took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for BioPAX took 0.25638556480407715s
Reputation | Calculation of the PageRank for BioPAX took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00010085105895996094s
Believability | Calculation of trust value for BioPAX took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-bp took 2.678767681121826s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 7.653236389160156e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.2531130313873291s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003254413604736328s
Believability | Calculation of trust value for Biomedical Resource Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.6325724124908447s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.25511598587036133s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002295970916748047s
Believability | Calculation of trust value for Spatial Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-bspo took 2.514354944229126s
Availability | SPARQL endpoint availability check for BioTop took 4.363059997558594e-05s
Availability | VoID file availability check for BioTop took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for BioTop took 0.26151108741760254s
Reputation | Calculation of the PageRank for BioTop took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for BioTop took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioTop took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006730556488037109s
Believability | Calculation of trust value for BioTop took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-bt took 2.6205832958221436s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.315376281738281e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0005574226379394531s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.26471996307373047s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.02059149742126465s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0009024143218994141s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-bto took 2.677417278289795s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.3285975456237793s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020591020584106445s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018312931060791016s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-canco took 3.068308115005493s
Availability | SPARQL endpoint availability check for CAO took 7.62939453125e-05s
Availability | VoID file availability check for CAO took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for CAO took 0.2596116065979004s
Reputation | Calculation of the PageRank for CAO took 0.020842313766479492s
Interlinking | Calculation of Degree of Connection for CAO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006375312805175781s
Believability | Calculation of trust value for CAO took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cao took 2.615355968475342s
Availability | SPARQL endpoint availability check for CareLex took 4.482269287109375e-05s
Availability | VoID file availability check for CareLex took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for CareLex took 0.2887890338897705s
Reputation | Calculation of the PageRank for CareLex took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for CareLex took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.935264587402344e-05s
Believability | Calculation of trust value for CareLex took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-carelex took 2.707944869995117s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00054168701171875s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.27228403091430664s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007898807525634766s
Believability | Calculation of trust value for Cell Cycle Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cco took 2.688366651535034s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.24531006813049316s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.00025343894958496094s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cdao took 2.5935115814208984s
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.0004904270172119141s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.2406914234161377s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020508289337158203s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007953643798828125s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007970333099365234s
Believability | Calculation of trust value for Chemical entities of biological interest took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-chebi took 2.645174264907837s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 4.482269287109375e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.27028489112854004s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002658367156982422s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.6478278636932373s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.24849987030029297s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007686614990234375s
Believability | Calculation of trust value for Chemical Information Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-cheminf took 2.539092779159546s
Availability | SPARQL endpoint availability check for Cell type took 6.914138793945312e-05s
Availability | VoID file availability check for Cell type took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Cell type took 0.28194570541381836s
Reputation | Calculation of the PageRank for Cell type took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for Cell type took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003788471221923828s
Believability | Calculation of trust value for Cell type took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-cl took 2.67268705368042s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 5.364418029785156e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005443096160888672s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.254178524017334s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020542621612548828s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008330345153808594s
Believability | Calculation of trust value for Cell Line Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-clo took 2.645024061203003s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.26531481742858887s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.02087116241455078s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.0001804828643798828s
Believability | Calculation of trust value for Clinical Measurement Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-cmo took 2.718998432159424s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 7.462501525878906e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.28330349922180176s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00021004676818847656s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cno took 2.7248034477233887s
Availability | SPARQL endpoint availability check for Wheat trait took 4.220008850097656e-05s
Availability | VoID file availability check for Wheat trait took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.28714871406555176s
Reputation | Calculation of the PageRank for Wheat trait took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for Wheat trait took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.2928924560546875e-05s
Believability | Calculation of trust value for Wheat trait took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-co_wheat took 2.6874284744262695s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 4.291534423828125e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.2590320110321045s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003418922424316406s
Believability | Calculation of trust value for Cognitive Atlas took 4.0531158447265625e-06s
INFO | --- Analysis for bioportal-cogat took 2.5659549236297607s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2666816711425781s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007593631744384766s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-cogpo took 2.693190097808838s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 4.3392181396484375e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2786381244659424s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004279613494873047s
Believability | Calculation of trust value for Current Procedural Terminology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cpt took 2.6844427585601807s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.172325134277344e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.31260228157043457s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020621538162231445s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017502307891845703s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-csp took 3.0790579319000244s
Availability | SPARQL endpoint availability check for COSTART took 4.315376281738281e-05s
Availability | VoID file availability check for COSTART took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for COSTART took 0.2626004219055176s
Reputation | Calculation of the PageRank for COSTART took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for COSTART took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COSTART took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009791851043701172s
Believability | Calculation of trust value for COSTART took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-cst took 2.5760483741760254s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.315376281738281e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.2745394706726074s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020519495010375977s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004928112030029297s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ctcae took 2.5780067443847656s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.267692565917969e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.2618546485900879s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004436969757080078s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ctx took 2.6171984672546387s
Availability | SPARQL endpoint availability check for Dendritic cell took 4.482269287109375e-05s
Availability | VoID file availability check for Dendritic cell took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.26711463928222656s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.0002899169921875s
Believability | Calculation of trust value for Dendritic cell took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.6098201274871826s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.649162292480469e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.2658653259277344s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.022039413452148438s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 0.00010561943054199219s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ddanat took 2.6125359535217285s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.291534423828125e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.26232457160949707s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.02033543586730957s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009522438049316406s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ddi took 2.569754123687744s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.2819705009460449s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020247459411621094s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.106231689453125e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.6520819664001465s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.24786949157714844s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.03255581855773926s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007965564727783203s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0002334117889404297s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.651036024093628s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Human disease ontology took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2434701919555664s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020200014114379883s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006260871887207031s
Believability | Calculation of trust value for Human disease ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-doid took 2.6956305503845215s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 5.7220458984375e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.2521042823791504s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.0208437442779541s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.000911712646484375s
Believability | Calculation of trust value for Electrocardiography Ontology took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-ecg took 2.600965976715088s
Availability | SPARQL endpoint availability check for Evidence codes took 5.14984130859375e-05s
Availability | VoID file availability check for Evidence codes took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.2504723072052002s
Reputation | Calculation of the PageRank for Evidence codes took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.218650817871094e-05s
Believability | Calculation of trust value for Evidence codes took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-eco took 2.6353156566619873s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 5.5789947509765625e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.3458395004272461s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017180442810058594s
Believability | Calculation of trust value for Experimental Factor Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-efo took 3.0701916217803955s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 5.2928924560546875e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.26022839546203613s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011632442474365234s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ehda took 2.6419169902801514s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.410743713378906e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.2691769599914551s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02063465118408203s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007960796356201172s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.5850985050201416s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.1484832763671875e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.27995848655700684s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020825624465942383s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005183219909667969s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.6611130237579346s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.220008850097656e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.28577113151550293s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020231246948242188s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.0279159545898438e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-emap took 2.6696345806121826s
Availability | SPARQL endpoint availability check for Environment Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Environment Ontology took 0.00039124488830566406s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.2540857791900635s
Reputation | Calculation of the PageRank for Environment Ontology took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00039386749267578125s
Believability | Calculation of trust value for Environment Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-envo took 2.6197943687438965s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 4.291534423828125e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.2583169937133789s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002968311309814453s
Believability | Calculation of trust value for Plant environmental conditions took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-eo took 2.603243350982666s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.24327588081359863s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.0012290477752685547s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ep took 2.5261380672454834s
Availability | SPARQL endpoint availability check for Epilepsy took 4.1961669921875e-05s
Availability | VoID file availability check for Epilepsy took 0.00041413307189941406s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.2802917957305908s
Reputation | Calculation of the PageRank for Epilepsy took 0.02035808563232422s
Interlinking | Calculation of Degree of Connection for Epilepsy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001285076141357422s
Believability | Calculation of trust value for Epilepsy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-epileponto took 2.5938351154327393s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.220008850097656e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0003180503845214844s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.261824369430542s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011546611785888672s
Believability | Calculation of trust value for eagle-i research resource ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ero took 2.619312047958374s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.38690185546875e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.2582106590270996s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011048316955566406s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ev took 2.614985466003418s
Availability | SPARQL endpoint availability check for ExO took 4.267692565917969e-05s
Availability | VoID file availability check for ExO took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for ExO took 0.29041314125061035s
Reputation | Calculation of the PageRank for ExO took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for ExO took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ExO took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00023984909057617188s
Believability | Calculation of trust value for ExO took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-exo took 2.6193370819091797s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.2697319984436035s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020505905151367188s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00011396408081054688s
Believability | Calculation of trust value for Fungal gross anatomy took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fao took 2.654257297515869s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.9591064453125e-05s
Availability | VoID file availability check for Biological imaging methods took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.25100207328796387s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.0001938343048095703s
Believability | Calculation of trust value for Biological imaging methods took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fbbi took 2.5777077674865723s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 4.267692565917969e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.2709493637084961s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006327629089355469s
Believability | Calculation of trust value for Drosophila gross anatomy took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbbt took 2.6789777278900146s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.25328755378723145s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020546674728393555s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004210472106933594s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbcv took 2.610766887664795s
Availability | SPARQL endpoint availability check for Drosophila development took 4.38690185546875e-05s
Availability | VoID file availability check for Drosophila development took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.2610347270965576s
Reputation | Calculation of the PageRank for Drosophila development took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for Drosophila development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.291534423828125e-05s
Believability | Calculation of trust value for Drosophila development took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-fbdv took 2.6483161449432373s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.1484832763671875e-05s
Availability | VoID file availability check for Fly taxonomy took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.2637619972229004s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003917217254638672s
Believability | Calculation of trust value for Fly taxonomy took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-fbsp took 2.6802139282226562s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.744529724121094e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.2919619083404541s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0008199214935302734s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00026154518127441406s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.6769185066223145s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.26874494552612305s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020445585250854492s
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.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.000457763671875s
Believability | Calculation of trust value for Family Health History Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-fhho took 2.647064447402954s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.553794860839844e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.28669118881225586s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020778179168701172s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.001104116439819336s
Believability | Calculation of trust value for Influenza Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-flu took 2.649204969406128s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.410743713378906e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.25621795654296875s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.246566772460938e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-fma took 2.5069425106048584s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.29146885871887207s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007996559143066406s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001316070556640625s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-fypo took 2.6820812225341797s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.2669548988342285s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 9.369850158691406e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-geospecies took 2.6617820262908936s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.24593639373779297s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00016188621520996094s
Believability | Calculation of trust value for General Formal Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gfo took 2.6608974933624268s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 9.655952453613281e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.2634592056274414s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005986690521240234s
Believability | Calculation of trust value for General Formal Ontology: Biology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.697143077850342s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 4.267692565917969e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.27382826805114746s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0009500980377197266s
Believability | Calculation of trust value for Gene Ontology Extension took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-go_x1 took 2.602998971939087s
Availability | SPARQL endpoint availability check for Gene Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Gene Ontology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2830805778503418s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020799875259399414s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008487701416015625s
Believability | Calculation of trust value for Gene Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.6744606494903564s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 6.961822509765625e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.28426218032836914s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.1948089599609375e-05s
Believability | Calculation of trust value for Cereal Plant Development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-gro took 2.562647581100464s
Availability | SPARQL endpoint availability check for Cereal plant gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Cereal plant gross anatomy took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.28171324729919434s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020842790603637695s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004360675811767578s
Believability | Calculation of trust value for Cereal plant gross anatomy took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.6194334030151367s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.2787508964538574s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007309913635253906s
Believability | Calculation of trust value for Gene Regulation Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.6944644451141357s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.2730560302734375s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005545616149902344s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-hao took 2.6563620567321777s
Availability | SPARQL endpoint availability check for HCPCS took 4.601478576660156e-05s
Availability | VoID file availability check for HCPCS took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2723276615142822s
Reputation | Calculation of the PageRank for HCPCS took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for HCPCS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for HCPCS took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00022339820861816406s
Believability | Calculation of trust value for HCPCS took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.64237380027771s
Availability | SPARQL endpoint availability check for Health Level Seven took 4.458427429199219e-05s
Availability | VoID file availability check for Health Level Seven took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.25643181800842285s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020797014236450195s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0013241767883300781s
Believability | Calculation of trust value for Health Level Seven took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-hl7 took 2.5845654010772705s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.38690185546875e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.27477025985717773s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003674030303955078s
Believability | Calculation of trust value for HEALTH_INDICATORS took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hlth_indics took 2.585350275039673s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 4.38690185546875e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.2477409839630127s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.170967102050781e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hom took 2.583287000656128s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.363059997558594e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2596147060394287s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.075599670410156e-05s
Believability | Calculation of trust value for HOM-HARVARD took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.606632709503174s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.2544221878051758s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.000659942626953125s
Believability | Calculation of trust value for Human Phenotype Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.5107014179229736s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 5.412101745605469e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.26107215881347656s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.001047372817993164s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-hpio took 2.5350584983825684s
Availability | SPARQL endpoint availability check for HUGO took 4.3392181396484375e-05s
Availability | VoID file availability check for HUGO took 0.0004165172576904297s
Completeness | Calculation of interlinking completeness for HUGO took 0.2599160671234131s
Reputation | Calculation of the PageRank for HUGO took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for HUGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for HUGO took 8.296966552734375e-05s
Believability | Calculation of trust value for HUGO took 4.744529724121094e-05s
INFO | --- Analysis for bioportal-hugo took 2.594416379928589s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 5.6743621826171875e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.24790239334106445s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006649494171142578s
Believability | Calculation of trust value for Information Artifact Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-iao took 2.559776782989502s
Availability | SPARQL endpoint availability check for ICD10 took 5.555152893066406e-05s
Availability | VoID file availability check for ICD10 took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for ICD10 took 0.27654099464416504s
Reputation | Calculation of the PageRank for ICD10 took 0.021015644073486328s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007796287536621094s
Believability | Calculation of trust value for ICD10 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-icd10 took 2.648401975631714s
Availability | SPARQL endpoint availability check for ICD10CM took 4.291534423828125e-05s
Availability | VoID file availability check for ICD10CM took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.271817684173584s
Reputation | Calculation of the PageRank for ICD10CM took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for ICD10CM took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006415843963623047s
Believability | Calculation of trust value for ICD10CM took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.7094719409942627s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.1484832763671875e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.26770853996276855s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00021767616271972656s
Believability | Calculation of trust value for ICD-10-PCS took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.6264255046844482s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 5.435943603515625e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.26662492752075195s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006322860717773438s
Believability | Calculation of trust value for International Classification of Diseases took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.6863842010498047s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2813863754272461s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.021007299423217773s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004820823669433594s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.7081987857818604s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 4.3392181396484375e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.26981019973754883s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012218952178955078s
Believability | Calculation of trust value for International Classification for Nursing Practice took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-icnp took 2.764864683151245s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 5.340576171875e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.3722507953643799s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004439353942871094s
Believability | Calculation of trust value for International Classification of Primary Care took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icpc took 2.740522623062134s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.410743713378906e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.2774696350097656s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0009312629699707031s
Believability | Calculation of trust value for ICPC-2 PLUS took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.5645511150360107s
Availability | SPARQL endpoint availability check for ICPS Network took 4.291534423828125e-05s
Availability | VoID file availability check for ICPS Network took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.2672762870788574s
Reputation | Calculation of the PageRank for ICPS Network took 0.020819664001464844s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0008270740509033203s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002684593200683594s
Believability | Calculation of trust value for ICPS Network took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-icps took 2.668647289276123s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2655186653137207s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.02014946937561035s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008869171142578125s
Believability | Calculation of trust value for Infectious Disease Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ido took 2.6031293869018555s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 7.319450378417969e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.26644277572631836s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011370182037353516s
Believability | Calculation of trust value for Brucellosis Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-idobru took 2.5515267848968506s
Availability | SPARQL endpoint availability check for Malaria Ontology took 5.054473876953125e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.27765607833862305s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0013043880462646484s
Believability | Calculation of trust value for Malaria Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-idomal took 2.6471991539001465s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.2438507080078125e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.2585172653198242s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003006458282470703s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-iev took 2.6418967247009277s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.267692565917969e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.2677345275878906s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00015687942504882812s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-imgt took 2.6286745071411133s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.267692565917969e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.27558422088623047s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020547866821289062s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005242824554443359s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-imr took 2.652879476547241s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.506111145019531e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.261782169342041s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020422697067260742s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008394718170166016s
Believability | Calculation of trust value for Interaction Network Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ino took 2.5640628337860107s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.363059997558594e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.2673909664154053s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020703792572021484s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0009391307830810547s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.361701965332031e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.628455638885498s
Availability | SPARQL endpoint availability check for IxnO took 4.38690185546875e-05s
Availability | VoID file availability check for IxnO took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for IxnO took 0.25815367698669434s
Reputation | Calculation of the PageRank for IxnO took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for IxnO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IxnO took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0001926422119140625s
Believability | Calculation of trust value for IxnO took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ixno took 2.6327176094055176s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.363059997558594e-05s
Availability | VoID file availability check for SysMO-JERM took 0.0007176399230957031s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.26962876319885254s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.021071910858154297s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0004143714904785156s
Believability | Calculation of trust value for SysMO-JERM took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-jerm took 2.6425299644470215s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.25218844413757324s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020484209060668945s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-kisao took 2.6100239753723145s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.410743713378906e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.2931389808654785s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00020074844360351562s
Believability | Calculation of trust value for Loggerhead nesting took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-lhn took 2.6756908893585205s
Availability | SPARQL endpoint availability check for Lipid Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.27310633659362793s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.020501375198364258s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00020813941955566406s
Believability | Calculation of trust value for Lipid Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-lipro took 2.657010316848755s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 8.392333984375e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.3072175979614258s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018160343170166016s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-lnc took 2.9564616680145264s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.220008850097656e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.24051165580749512s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006554126739501953s
Believability | Calculation of trust value for Mouse adult gross anatomy took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ma took 2.6416962146759033s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.2438507080078125e-05s
Availability | VoID file availability check for Multiple alignment took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.25314855575561523s
Reputation | Calculation of the PageRank for Multiple alignment took 0.02116250991821289s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00022530555725097656s
Believability | Calculation of trust value for Multiple alignment took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mao took 2.5597422122955322s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.291534423828125e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.25399184226989746s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0009541511535644531s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0007679462432861328s
Believability | Calculation of trust value for Minimal anatomical terminology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mat took 2.6649630069732666s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 4.315376281738281e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0005857944488525391s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.27213120460510254s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0007951259613037109s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004467964172363281s
Believability | Calculation of trust value for Breast tissue cell lines took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.5988597869873047s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005774497985839844s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2649989128112793s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021973848342895508s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0010790824890136719s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0008585453033447266s
Believability | Calculation of trust value for Cell line ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mccl took 2.6956889629364014s
Availability | SPARQL endpoint availability check for Cell line ontology took 5.0067901611328125e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.2440478801727295s
Reputation | Calculation of the PageRank for Cell line ontology took 0.021339893341064453s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0010781288146972656s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.001615762710571289s
Believability | Calculation of trust value for Cell line ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.582651376724243s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.3392181396484375e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.2593348026275635s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.020332813262939453s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00023698806762695312s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mcv took 2.6499807834625244s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 4.267692565917969e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.2534656524658203s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017142295837402344s
Believability | Calculation of trust value for Master Drug Data Base took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mddb took 2.6253714561462402s
Availability | SPARQL endpoint availability check for MedDRA took 4.172325134277344e-05s
Availability | VoID file availability check for MedDRA took 0.0011544227600097656s
Completeness | Calculation of interlinking completeness for MedDRA took 0.27534985542297363s
Reputation | Calculation of the PageRank for MedDRA took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011985301971435547s
Believability | Calculation of trust value for MedDRA took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mdr took 2.5941245555877686s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 7.557868957519531e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005452632904052734s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.28008341789245605s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0009059906005859375s
Believability | Calculation of trust value for MedlinePlus Health Topics took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.648603916168213s
Availability | SPARQL endpoint availability check for MeGO took 5.793571472167969e-05s
Availability | VoID file availability check for MeGO took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for MeGO took 0.2693328857421875s
Reputation | Calculation of the PageRank for MeGO took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for MeGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.00017547607421875s
Believability | Calculation of trust value for MeGO took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mego took 2.6817283630371094s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.363059997558594e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.30295658111572266s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007746219635009766s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018334388732910156s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-mesh-owl took 3.061995029449463s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2681868076324463s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006091594696044922s
Believability | Calculation of trust value for Mental Functioning Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mf took 2.7649011611938477s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.291534423828125e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.2753422260284424s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020452499389648438s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005743503570556641s
Believability | Calculation of trust value for Medaka fish anatomy and development took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mfo took 2.664787530899048s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0005729198455810547s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.28211379051208496s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007627010345458984s
Believability | Calculation of trust value for Emotion Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-mfoem took 2.6727142333984375s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.26499223709106445s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.020998477935791016s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00011181831359863281s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mhc took 2.60514760017395s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 4.267692565917969e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.26744937896728516s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006871223449707031s
Believability | Calculation of trust value for Protein-protein interaction took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mi took 2.628305435180664s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.363059997558594e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2676248550415039s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0007288455963134766s
Believability | Calculation of trust value for Mosquito insecticide resistance took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-miro took 2.630643129348755s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.2691841125488281s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013947486877441406s
Believability | Calculation of trust value for Measurement Method Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-mmo took 2.629246473312378s
Availability | SPARQL endpoint availability check for MGED Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for MGED Ontology took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.2690246105194092s
Reputation | Calculation of the PageRank for MGED Ontology took 0.021553754806518555s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0008440017700195312s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0004723072052001953s
Believability | Calculation of trust value for MGED Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mo took 2.601369857788086s
Availability | SPARQL endpoint availability check for Protein modification took 4.2438507080078125e-05s
Availability | VoID file availability check for Protein modification took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Protein modification took 0.26666760444641113s
Reputation | Calculation of the PageRank for Protein modification took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.0002193450927734375s
Believability | Calculation of trust value for Protein modification took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-mod took 2.584676504135132s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 7.009506225585938e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.26474833488464355s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006496906280517578s
Believability | Calculation of trust value for Mammalian phenotype took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-mp took 2.5553677082061768s
Availability | SPARQL endpoint availability check for Mouse pathology took 4.482269287109375e-05s
Availability | VoID file availability check for Mouse pathology took 0.0005705356597900391s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.28774523735046387s
Reputation | Calculation of the PageRank for Mouse pathology took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.0004801750183105469s
Believability | Calculation of trust value for Mouse pathology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-mpath took 2.6573736667633057s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.744529724121094e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0008139610290527344s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.24083900451660156s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.021192550659179688s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0003688335418701172s
Believability | Calculation of trust value for Mass spectrometry took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-ms took 2.6676292419433594s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.267692565917969e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.3129739761352539s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.001888275146484375s
Believability | Calculation of trust value for Medical Subject Headings took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-msh took 3.131659507751465s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.267692565917969e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.27107882499694824s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02086639404296875s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00018262863159179688s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-mthch took 2.5684807300567627s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 5.340576171875e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.25775146484375s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007724761962890625s
Believability | Calculation of trust value for Natural Products Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-natpro took 2.6252946853637695s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.5299530029296875e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2567009925842285s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008139610290527344s
Believability | Calculation of trust value for NCBI organismal classification took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ncbitaxon took 2.610530138015747s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2961716651916504s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020508766174316406s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002004861831665039s
Believability | Calculation of trust value for NCI Thesaurus took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-ncit took 2.9584059715270996s
Availability | SPARQL endpoint availability check for National Drug Data File took 4.482269287109375e-05s
Availability | VoID file availability check for National Drug Data File took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.26660633087158203s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006198883056640625s
Believability | Calculation of trust value for National Drug Data File took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-nddf took 2.6710288524627686s
Availability | SPARQL endpoint availability check for National Drug File took 4.267692565917969e-05s
Availability | VoID file availability check for National Drug File took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for National Drug File took 0.2646749019622803s
Reputation | Calculation of the PageRank for National Drug File took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for National Drug File took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Drug File took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.0012226104736328125s
Believability | Calculation of trust value for National Drug File took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ndfrt took 2.56170916557312s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.172325134277344e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.294644832611084s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011792182922363281s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.661498546600342s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.2786409854888916s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006740093231201172s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-neomark took 2.6184558868408203s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0011816024780273438s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2760162353515625s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00012421607971191406s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.6122584342956543s
Availability | SPARQL endpoint availability check for NIFSTD took 4.363059997558594e-05s
Availability | VoID file availability check for NIFSTD took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.3059248924255371s
Reputation | Calculation of the PageRank for NIFSTD took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for NIFSTD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIFSTD took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018734931945800781s
Believability | Calculation of trust value for NIFSTD took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-nif took 2.9513251781463623s
Availability | SPARQL endpoint availability check for NIF Cell took 4.6253204345703125e-05s
Availability | VoID file availability check for NIF Cell took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.2696206569671631s
Reputation | Calculation of the PageRank for NIF Cell took 0.020878314971923828s
Interlinking | Calculation of Degree of Connection for NIF Cell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Cell took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.0014050006866455078s
Believability | Calculation of trust value for NIF Cell took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-nif_cell took 2.6462879180908203s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 4.315376281738281e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.2853708267211914s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.001390218734741211s
Believability | Calculation of trust value for NIF Dysfunction took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.618990182876587s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.26800036430358887s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005571842193603516s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 3.814697265625e-06s
INFO | --- Analysis for bioportal-nigo took 2.6955947875976562s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.38690185546875e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.2657930850982666s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020441770553588867s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005679130554199219s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 9.5367431640625e-06s
INFO | --- Analysis for bioportal-nmr took 2.581444025039673s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.2657742500305176s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010752677917480469s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.591522216796875s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 5.698204040527344e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.25001955032348633s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02080678939819336s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011706352233886719s
Believability | Calculation of trust value for NanoParticle Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-npo took 2.5760581493377686s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.458427429199219e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.2722001075744629s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007581710815429688s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-oae took 2.488297939300537s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.8160552978515625e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.26529979705810547s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020453214645385742s
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.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014581680297851562s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-obi took 2.674974203109741s
Availability | SPARQL endpoint availability check for OBOE took 4.315376281738281e-05s
Availability | VoID file availability check for OBOE took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for OBOE took 0.24482178688049316s
Reputation | Calculation of the PageRank for OBOE took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for OBOE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OBOE took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00011420249938964844s
Believability | Calculation of trust value for OBOE took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-oboe took 2.560281276702881s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.291534423828125e-05s
Availability | VoID file availability check for OBOE SBC took 0.0005352497100830078s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2798314094543457s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020394563674926758s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007898807525634766s
Believability | Calculation of trust value for OBOE SBC took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-oboe-sbc took 2.6342499256134033s
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.0004737377166748047s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2718236446380615s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005831718444824219s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ocre took 2.6633124351501465s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.6253204345703125e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.2734541893005371s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.0210268497467041s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008592605590820312s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-odgi took 2.6706550121307373s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 4.458427429199219e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2542400360107422s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.020325422286987305s
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.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008642673492431641s
Believability | Calculation of trust value for Ontology for Genetic Interval took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-ogi took 2.572310209274292s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2707216739654541s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00028705596923828125s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ogmd took 2.6510066986083984s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 4.220008850097656e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.29169678688049316s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.03447318077087402s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0016033649444580078s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.00113677978515625s
Believability | Calculation of trust value for Ontology for General Medical Science took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ogms took 2.650570869445801s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 5.4836273193359375e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.2883474826812744s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020853281021118164s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.0011568069458007812s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-omim took 2.6598892211914062s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.172325134277344e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.2586026191711426s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.000385284423828125s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-omit took 2.5539398193359375s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2695603370666504s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020379066467285156s
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.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0006418228149414062s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-omrse took 2.390385866165161s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.363059997558594e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.25737929344177246s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02046036720275879s
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.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.000782012939453125s
Believability | Calculation of trust value for Ontology of Data Mining took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-ontodm took 2.6210570335388184s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.8160552978515625e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0005807876586914062s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.28332066535949707s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002377033233642578s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.603172540664673s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 4.2438507080078125e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.274181604385376s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006053447723388672s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 9.298324584960938e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.6191000938415527s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 7.319450378417969e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.27460670471191406s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009012222290039062s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-opl took 2.6273226737976074s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.220008850097656e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2663583755493164s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008697509765625s
Believability | Calculation of trust value for Phenotypic quality took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-pato took 2.659003734588623s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.8160552978515625e-05s
Availability | VoID file availability check for Physician Data Query took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.2947399616241455s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.001064300537109375s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.001016378402709961s
Believability | Calculation of trust value for Physician Data Query took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-pdq took 2.672288656234741s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.315376281738281e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.28309035301208496s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007812976837158203s
Believability | Calculation of trust value for Pediatric Terminology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-pedterm took 2.632399559020996s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.26995205879211426s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020818233489990234s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019741058349609375s
Believability | Calculation of trust value for Parasite Experiment Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-peo took 2.634728193283081s
Availability | SPARQL endpoint availability check for PHARE took 4.3392181396484375e-05s
Availability | VoID file availability check for PHARE took 0.0010917186737060547s
Completeness | Calculation of interlinking completeness for PHARE took 0.2760286331176758s
Reputation | Calculation of the PageRank for PHARE took 0.020359516143798828s
Interlinking | Calculation of Degree of Connection for PHARE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006394386291503906s
Believability | Calculation of trust value for PHARE took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-phare took 2.6892311573028564s
Availability | SPARQL endpoint availability check for PKO_Re took 4.38690185546875e-05s
Availability | VoID file availability check for PKO_Re took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2636294364929199s
Reputation | Calculation of the PageRank for PKO_Re took 0.020987987518310547s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00019693374633789062s
Believability | Calculation of trust value for PKO_Re took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-pko took 2.593799114227295s
Availability | SPARQL endpoint availability check for PMA 2010 took 5.793571472167969e-05s
Availability | VoID file availability check for PMA 2010 took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.27123069763183594s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020691633224487305s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007610321044921875s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009162425994873047s
Believability | Calculation of trust value for PMA 2010 took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-pma took 2.6233179569244385s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.4345855712890625e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.28318023681640625s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00017547607421875s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-pmr took 2.6581318378448486s
Availability | SPARQL endpoint availability check for Plant Anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Plant Anatomy took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.2670886516571045s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.0004031658172607422s
Believability | Calculation of trust value for Plant Anatomy took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-po took 2.610609292984009s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 5.2928924560546875e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0005130767822265625s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.26822590827941895s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.0207977294921875s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 7.510185241699219e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.52587890625e-05s
INFO | --- Analysis for bioportal-po_x1 took 2.6721324920654297s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Plant Ontology took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.26709890365600586s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004477500915527344s
Believability | Calculation of trust value for Plant Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.669764518737793s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.363059997558594e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.25277113914489746s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006577968597412109s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-pr took 2.52062726020813s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.4345855712890625e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.2539713382720947s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007762908935546875s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.000270843505859375s
Believability | Calculation of trust value for Proteomics data and process provenance took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-propreo took 2.6180760860443115s
Availability | SPARQL endpoint availability check for Pathway ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.256422758102417s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020714521408081055s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00013446807861328125s
Believability | Calculation of trust value for Pathway ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-pw took 2.581007957458496s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.24940276145935059s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.4809112548828125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-qibo took 2.6504080295562744s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.792213439941406e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.3040142059326172s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02034759521484375s
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.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.001786947250366211s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rcd took 3.0263335704803467s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.25882411003112793s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.001032114028930664s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001671314239501953s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rctontology took 2.5983901023864746s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.601478576660156e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.27901601791381836s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020554542541503906s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.846687316894531e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-repo took 2.700003147125244s
Availability | SPARQL endpoint availability check for Physico-chemical process took 4.482269287109375e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.3281064033508301s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019049644470214844s
Believability | Calculation of trust value for Physico-chemical process took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-rex took 2.7313694953918457s
Availability | SPARQL endpoint availability check for RadLex took 4.38690185546875e-05s
Availability | VoID file availability check for RadLex took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for RadLex took 0.2725405693054199s
Reputation | Calculation of the PageRank for RadLex took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for RadLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015456676483154297s
Believability | Calculation of trust value for RadLex took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rid took 2.5331528186798096s
Availability | SPARQL endpoint availability check for RNA ontology took 4.458427429199219e-05s
Availability | VoID file availability check for RNA ontology took 0.0005450248718261719s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.28286004066467285s
Reputation | Calculation of the PageRank for RNA ontology took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for RNA ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005648136138916016s
Believability | Calculation of trust value for RNA ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-rnao took 2.6612892150878906s
Availability | SPARQL endpoint availability check for Role Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Role Ontology took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.2832376956939697s
Reputation | Calculation of the PageRank for Role Ontology took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00020170211791992188s
Believability | Calculation of trust value for Role Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-roleo took 2.648510217666626s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.27734851837158203s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001842975616455078s
Believability | Calculation of trust value for Rat Strain Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-rs took 2.5938191413879395s
Availability | SPARQL endpoint availability check for RxNORM took 4.6253204345703125e-05s
Availability | VoID file availability check for RxNORM took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2848820686340332s
Reputation | Calculation of the PageRank for RxNORM took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for RxNORM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006136894226074219s
Believability | Calculation of trust value for RxNORM took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.6578209400177s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.935264587402344e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.26630568504333496s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010612010955810547s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sao took 2.579446792602539s
Availability | SPARQL endpoint availability check for Systems Biology took 6.341934204101562e-05s
Availability | VoID file availability check for Systems Biology took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.5345635414123535s
Reputation | Calculation of the PageRank for Systems Biology took 0.020689010620117188s
Interlinking | Calculation of Degree of Connection for Systems Biology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004520416259765625s
Believability | Calculation of trust value for Systems Biology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-sbo took 2.937256336212158s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 4.696846008300781e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0006158351898193359s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.27867913246154785s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0009837150573730469s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00013256072998046875s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-sbro took 2.8271324634552s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 4.458427429199219e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.25544071197509766s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0013120174407958984s
Believability | Calculation of trust value for Sleep Domain Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-sdo took 2.6044108867645264s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.291534423828125e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2837977409362793s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00034165382385253906s
Believability | Calculation of trust value for Sample processing and separation techniques took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-sep took 2.624156951904297s
Availability | SPARQL endpoint availability check for Student Health Record took 4.506111145019531e-05s
Availability | VoID file availability check for Student Health Record took 0.0006203651428222656s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.25493431091308594s
Reputation | Calculation of the PageRank for Student Health Record took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.00045228004455566406s
Believability | Calculation of trust value for Student Health Record took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-shr took 2.5228309631347656s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0006852149963378906s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.25487661361694336s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02018451690673828s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012352466583251953s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sio took 3.7085120677948s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 4.38690185546875e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0010404586791992188s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2671525478363037s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00020313262939453125s
Believability | Calculation of trust value for Situation-Based Access Control took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-sitbac took 2.5596394538879395s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.506111145019531e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0005590915679931641s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.3161911964416504s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02095818519592285s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019528865814208984s
Believability | Calculation of trust value for SNOMED Clinical Terms took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-snomedct took 2.998732089996338s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.33079051971435547s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020081758499145508s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006914138793945312s
Believability | Calculation of trust value for SNP-Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-snpo took 2.626858711242676s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.267692565917969e-05s
Availability | VoID file availability check for Sequence types and features took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2845330238342285s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005755424499511719s
Believability | Calculation of trust value for Sequence types and features took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.6200382709503174s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.482269287109375e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.30077290534973145s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015711784362792969s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-sopharm took 3.039306879043579s
Availability | SPARQL endpoint availability check for SoyOntology took 4.267692565917969e-05s
Availability | VoID file availability check for SoyOntology took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.28079676628112793s
Reputation | Calculation of the PageRank for SoyOntology took 0.02031540870666504s
Interlinking | Calculation of Degree of Connection for SoyOntology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001220703125s
Believability | Calculation of trust value for SoyOntology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-soy took 2.6351616382598877s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Spider Ontology took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.25794291496276855s
Reputation | Calculation of the PageRank for Spider Ontology took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.0003304481506347656s
Believability | Calculation of trust value for Spider Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-spd took 2.59440016746521s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.28119826316833496s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.021539926528930664s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0010530948638916016s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.0003643035888671875s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-spto took 2.540816307067871s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.2839024066925049s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004360675811767578s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-sso took 2.6291401386260986s
Availability | SPARQL endpoint availability check for Software Ontology took 5.5789947509765625e-05s
Availability | VoID file availability check for Software Ontology took 0.0003540515899658203s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.25252819061279297s
Reputation | Calculation of the PageRank for Software Ontology took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for Software Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00039887428283691406s
Believability | Calculation of trust value for Software Ontology took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-swo took 2.6742539405822754s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 4.291534423828125e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.28371357917785645s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023102760314941406s
Believability | Calculation of trust value for Tick gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tads took 2.6701276302337646s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.27460217475891113s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.02055644989013672s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008697509765625s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-tao took 2.616647958755493s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.4345855712890625e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.25113606452941895s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.58306884765625e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 4.291534423828125e-06s
INFO | --- Analysis for bioportal-taxrank took 2.6110501289367676s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.363059997558594e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.26999711990356445s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.020270586013793945s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.486343383789062e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-teddy took 2.6562836170196533s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.2547883987426758s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020578861236572266s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 4.124641418457031e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008339881896972656s
Believability | Calculation of trust value for Time Event Ontology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-teo took 2.5497944355010986s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.26225829124450684s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.0003895759582519531s
Believability | Calculation of trust value for Mosquito gross anatomy took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-tgma took 2.5686964988708496s
Availability | SPARQL endpoint availability check for thesaurus took 4.458427429199219e-05s
Availability | VoID file availability check for thesaurus took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for thesaurus took 0.26565027236938477s
Reputation | Calculation of the PageRank for thesaurus took 0.020433664321899414s
Interlinking | Calculation of Degree of Connection for thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for thesaurus took 8.940696716308594e-05s
Believability | Calculation of trust value for thesaurus took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.6279380321502686s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.3392181396484375e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.2626302242279053s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.00033736228942871094s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.627837896347046s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.363059997558594e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2707188129425049s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020793676376342773s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007777214050292969s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0009477138519287109s
Believability | Calculation of trust value for Translational Medicine Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-tmo took 2.6601665019989014s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.2508666515350342s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015497207641601562s
Believability | Calculation of trust value for Plant Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-to took 2.5170233249664307s
Availability | SPARQL endpoint availability check for TOK_Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0005509853363037109s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.292464017868042s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.0001838207244873047s
Believability | Calculation of trust value for TOK_Ontology took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-tok took 2.6524298191070557s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.291534423828125e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.23923373222351074s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00021314620971679688s
Believability | Calculation of trust value for Teleost taxonomy took 3.814697265625e-06s
INFO | --- Analysis for bioportal-tto took 2.629030466079712s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.26773524284362793s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010247230529785156s
Believability | Calculation of trust value for Uber anatomy ontology took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-uberon took 2.648535966873169s
Availability | SPARQL endpoint availability check for Units Ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Units Ontology took 0.0005662441253662109s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.26877546310424805s
Reputation | Calculation of the PageRank for Units Ontology took 0.020290374755859375s
Interlinking | Calculation of Degree of Connection for Units Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002281665802001953s
Believability | Calculation of trust value for Units Ontology took 5.245208740234375e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.650298595428467s
Availability | SPARQL endpoint availability check for Units of measurement took 4.291534423828125e-05s
Availability | VoID file availability check for Units of measurement took 0.0003752708435058594s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.2612903118133545s
Reputation | Calculation of the PageRank for Units of measurement took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Units of measurement took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.0002803802490234375s
Believability | Calculation of trust value for Units of measurement took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-uo took 2.617967128753662s
Availability | SPARQL endpoint availability check for VANDF took 4.363059997558594e-05s
Availability | VoID file availability check for VANDF took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for VANDF took 0.2660644054412842s
Reputation | Calculation of the PageRank for VANDF took 0.020224571228027344s
Interlinking | Calculation of Degree of Connection for VANDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for VANDF took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.000682830810546875s
Believability | Calculation of trust value for VANDF took 4.5299530029296875e-06s
INFO | --- Analysis for bioportal-vandf took 2.6670374870300293s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2739086151123047s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004355907440185547s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vao took 2.575399398803711s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 4.220008850097656e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.2679252624511719s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.022313594818115234s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007920265197753906s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006763935089111328s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vhog took 2.6739704608917236s
Availability | SPARQL endpoint availability check for VIVO took 4.291534423828125e-05s
Availability | VoID file availability check for VIVO took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for VIVO took 0.2627265453338623s
Reputation | Calculation of the PageRank for VIVO took 0.020339012145996094s
Interlinking | Calculation of Degree of Connection for VIVO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00035834312438964844s
Believability | Calculation of trust value for VIVO took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-vivo took 2.6592228412628174s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.2795064449310303s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020308971405029297s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012731552124023438s
Believability | Calculation of trust value for Vaccine Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-vo took 2.6776111125946045s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.2830359935760498s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.020427703857421875s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0008218288421630859s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00023698806762695312s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-vt took 2.5778207778930664s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.363059997558594e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.26633238792419434s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.0004897117614746094s
Believability | Calculation of trust value for C. elegans gross anatomy took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-wbbt took 2.6036126613616943s
Availability | SPARQL endpoint availability check for C. elegans development took 4.506111145019531e-05s
Availability | VoID file availability check for C. elegans development took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.2757699489593506s
Reputation | Calculation of the PageRank for C. elegans development took 0.02016425132751465s
Interlinking | Calculation of Degree of Connection for C. elegans development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.291534423828125e-05s
Believability | Calculation of trust value for C. elegans development took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-wbls took 2.6804914474487305s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.2438507080078125e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2686147689819336s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.7738037109375e-05s
Believability | Calculation of trust value for C. elegans phenotype took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.6490440368652344s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.363059997558594e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0003521442413330078s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2713456153869629s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020583629608154297s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0006315708160400391s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 5.4836273193359375e-06s
INFO | --- Analysis for bioportal-who took 2.619636297225952s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 6.866455078125e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.0005636215209960938s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.25449419021606445s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006654262542724609s
Believability | Calculation of trust value for Xenopus anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-xao took 2.6414828300476074s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2533748149871826s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.0002498626708984375s
Believability | Calculation of trust value for Experimental Conditions Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-xco took 2.6096670627593994s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 4.267692565917969e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2542593479156494s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00026869773864746094s
Believability | Calculation of trust value for Yeast phenotypes took 4.76837158203125e-06s
INFO | --- Analysis for bioportal-ypo took 2.6543140411376953s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.1484832763671875e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2510247230529785s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020198345184326172s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007927417755126953s
Believability | Calculation of trust value for Zebrafish anatomy and development took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-zfa took 2.632861852645874s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.410743713378906e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0012993812561035156s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.268873929977417s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 6.4373016357421875e-06s
INFO | --- Analysis for Bioportal_link took 3.806842088699341s
Availability | SPARQL endpoint availability check for BioSamples RDF took 0.46341443061828613s
Availability | VoID file availability check for BioSamples RDF took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.28264498710632324s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.02055048942565918s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.3855438232421875e-05s
Believability | Calculation of trust value for BioSamples RDF took 6.67572021484375e-06s
INFO | --- Analysis for biosamples-rdf took 3.5086419582366943s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 0.44821691513061523s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2513422966003418s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00011539459228515625s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for bis-linked-data took 2.9131906032562256s
Availability | SPARQL endpoint availability check for Bitzi took 4.57763671875e-05s
Availability | VoID file availability check for Bitzi took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Bitzi took 0.2598893642425537s
Reputation | Calculation of the PageRank for Bitzi took 0.020505666732788086s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Bitzi took 3.0279159545898438e-05s
Believability | Calculation of trust value for Bitzi took 6.9141387939453125e-06s
INFO | --- Analysis for bitzi took 2.874420642852783s
Availability | SPARQL endpoint availability check for BizkaiSense took 4.220008850097656e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.2857983112335205s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020287036895751953s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.0040740966796875e-05s
Believability | Calculation of trust value for BizkaiSense took 7.152557373046875e-06s
INFO | --- Analysis for bizkaisense took 2.917128086090088s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.1961669921875e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2546374797821045s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.9325485229492188e-05s
Believability | Calculation of trust value for blabla.itemlist took 6.9141387939453125e-06s
INFO | --- Analysis for blabla-itemlist took 2.823637008666992s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.2438507080078125e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.26828432083129883s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.8133392333984375e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.152557373046875e-06s
INFO | --- Analysis for blabla_itemlist took 2.861433267593384s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.5299530029296875e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2677748203277588s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.076957702636719e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for bll-thesaurus took 3.5571939945220947s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.701357126235962s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.25232553482055664s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.021583080291748047s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 7.319450378417969e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for bluk-bnb took 13.7328040599823s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.2757441997528076s
Availability | VoID file availability check for Thesaurus BNCF took 0.00047326087951660156s
Extra | Recovery of all triples for Thesaurus BNCF took 72.68639898300171s
Performance | Total latancy measurement for Thesaurus BNCF took 0.5773191452026367s
Amount of data | Number of triples check for Thesaurus BNCF took 1.177459716796875s
Interoperability | New terms check for Thesaurus BNCF took 1.5290584564208984s
Versatility | Languages check for Thesaurus BNCF took 12.054104328155518s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 1.614567756652832s
Security | Check HTTPS for Thesaurus BNCF took 0.0735781192779541s
Interpretability | RDF structures check for Thesaurus BNCF took 0.11180710792541504s
Versatility | Serialization formats check for Thesaurus BNCF took 0.1191408634185791s
Availability | RDF dump link check for Thesaurus BNCF took 0.11382651329040527s
License | MR license check for Thesaurus BNCF took 0.11562228202819824s
License | HR license check for Thesaurus BNCF took 0.274639368057251s
Amount of data | Number of property check for Thesaurus BNCF took 0.11140727996826172s
Understandability | Number of label check for Thesaurus BNCF took 0.37520623207092285s
Understandability | URI regex check for Thesaurus BNCF took 0.23648929595947266s
Understandability | Vocabs check for Thesaurus BNCF took 0.10799431800842285s
Verifiability | Authors check for Thesaurus BNCF took 0.11788344383239746s
Verifiability | Publishers check for Thesaurus BNCF took 0.11659908294677734s
Performance | Throughput check for Thesaurus BNCF took 10.550418853759766s
Amount of data | Check the number of entities for Thesaurus BNCF took 0.00014400482177734375s
Verifiability | Contribs. check for Thesaurus BNCF took 0.11022520065307617s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.11501407623291016s
Interlinking | skos check for Thesaurus BNCF took 0.2160191535949707s
Interlinking | skos check for Thesaurus BNCF took 0.18688416481018066s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.12080073356628418s
Currency | Creation date check for Thesaurus BNCF took 0.22841715812683105s
Currency | Modification date check for Thesaurus BNCF took 0.2229480743408203s
Rep.Conc. | URIs length for Thesaurus BNCF took 29.210681676864624s
Interoperability | New vocabularies check for Thesaurus BNCF took 1.71661376953125e-05s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.11231374740600586s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.10921430587768555s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.11478614807128906s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.247615575790405s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5094361305236816s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.8933563232421875s
Consistency | Disjoint class check for Thesaurus BNCF took 0.11291956901550293s
Consistency | Check Misplaced properties for Thesaurus BNCF took 1.438591718673706s
Consistency | Misplaced classes for Thesaurus BNCF took 6.8141279220581055s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 9.093942165374756s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4378883838653564s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.7955820560455322s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.4465243816375732s
Security | Sign check for Thesaurus BNCF took 0.1309809684753418s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.706860780715942s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.38931846618652344s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020043134689331055s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0018954277038574219s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 7.414817810058594e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.9073486328125e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 9.5367431640625e-06s
INFO | --- Analysis for bncf-ns took 231.08069109916687s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.6947104930877686s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0004956722259521484s
Extra | Recovery of all triples for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9858357906341553s
Performance | Total latancy measurement for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.2992494106292725s
Amount of data | Number of triples check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.902315139770508s
Interoperability | New terms check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.513510227203369s
Versatility | Languages check for BPR ? Bibliography of the Italian Parliament and electoral studies took 60.31882905960083s
Interpretability | Number of blank nodes check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.72254753112793s
Security | Check HTTPS for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2688636779785156s
Interpretability | RDF structures check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8053081035614014s
Versatility | Serialization formats check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.075230598449707s
Availability | RDF dump link check for BPR ? Bibliography of the Italian Parliament and electoral studies took 5.166173458099365s
License | MR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.6156442165374756s
License | HR license check for BPR ? Bibliography of the Italian Parliament and electoral studies took 61.855494260787964s
Amount of data | Number of property check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.37904906272888184s
Understandability | Number of label check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.947413682937622s
Understandability | URI regex check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.0889744758605957s
Understandability | Vocabs check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.7521090507507324s
Verifiability | Authors check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.5124399662017822s
Verifiability | Publishers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3219749927520752s
Performance | Throughput check for BPR ? Bibliography of the Italian Parliament and electoral studies took 20.680742740631104s
Amount of data | Check the number of entities for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.414817810058594e-05s
Verifiability | Contribs. check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3718080520629883s
Interlinking | sameAs chians check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.839242935180664s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.741504430770874s
Interlinking | skos check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3170816898345947s
Timeliness | dataset update frequency check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.213897228240967s
Currency | Creation date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.1470465660095215s
Currency | Modification date check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.2396705150604248s
Rep.Conc. | URIs length for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.6478111743927s
Interoperability | New vocabularies check for BPR ? Bibliography of the Italian Parliament and electoral studies took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for BPR ? Bibliography of the Italian Parliament and electoral studies took 13.521904945373535s
Accuracy | Check Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.4066007137298584s
Accuracy | Check Inverse Functional Property for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.3527543544769287s
Accuracy | Check Empty annotation labels for BPR ? Bibliography of the Italian Parliament and electoral studies took 27.796313285827637s
Accuracy | Check White space in annotation for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02407217025756836s
Accuracy | Check Datatype consistency for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02946162223815918s
Consistency | Disjoint class check for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.016211748123169s
Consistency | Check Misplaced properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 23.10629105567932s
Consistency | Misplaced classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.7380454540252686s
Consistency | Check Ontology hijacking for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.368738651275635s
Consistency | Check Invalid usage of undefined classes for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.5739874839782715s
Consistency | Check Invalid usage of undefined properties for BPR ? Bibliography of the Italian Parliament and electoral studies took 15.178354978561401s
Conciseness | Check Extensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.031072616577148438s
Conciseness | Check Intensional conciseness for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.193943977355957s
Security | Sign check for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.964322805404663s
Availability | Check URIs Dereferenciability for BPR ? Bibliography of the Italian Parliament and electoral studies took 11.250731945037842s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.8035242557525635s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02064990997314453s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.458427429199219e-05s
Interoperability | Check the re-using of existing vocabs for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.9073486328125e-06s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 7.152557373046875e-06s
INFO | --- Analysis for bpr took 858.2818567752838s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.482269287109375e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.7095303535461426s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.295608520507812e-05s
Believability | Calculation of trust value for Brazilian Politicians took 5.245208740234375e-06s
INFO | --- Analysis for brazilian-politicians took 4.561744689941406s
Availability | SPARQL endpoint availability check for BrazilianCities took 3.9577484130859375e-05s
Availability | VoID file availability check for BrazilianCities took 0.00039649009704589844s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.6989877223968506s
Reputation | Calculation of the PageRank for BrazilianCities took 0.02042865753173828s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.0279159545898438e-05s
Believability | Calculation of trust value for BrazilianCities took 1.2636184692382812e-05s
INFO | --- Analysis for braziliancities took 4.6267335414886475s
Availability | SPARQL endpoint availability check for Bricklink took 1.7012064456939697s
Availability | VoID file availability check for Bricklink took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for Bricklink took 0.706028938293457s
Reputation | Calculation of the PageRank for Bricklink took 0.02242279052734375s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0008058547973632812s
Interlinking | Calculation of Clustering coefficient for Bricklink took 9.465217590332031e-05s
Believability | Calculation of trust value for Bricklink took 7.3909759521484375e-06s
INFO | --- Analysis for bricklink took 10.019855976104736s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.152389764785767s
Availability | VoID file availability check for British Museum Collection took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2805185317993164s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02064824104309082s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 3.0994415283203125e-05s
Believability | Calculation of trust value for British Museum Collection took 7.62939453125e-06s
INFO | --- Analysis for british-museum-collection took 73.00930261611938s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.315376281738281e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2962002754211426s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.910064697265625e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 7.62939453125e-06s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 4.211460590362549s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.76837158203125e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.27873969078063965s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02053213119506836s
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.0007088184356689453s
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 7.3909759521484375e-06s
INFO | --- Analysis for bsv took 2.965940237045288s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 3.0703840255737305s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.00039267539978027344s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.26346635818481445s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.33514404296875e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 6.4373016357421875e-06s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 7.370578289031982s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 9.202957153320312e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.2605254650115967s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020003318786621094s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.956390380859375e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 6.4373016357421875e-06s
INFO | --- Analysis for bund-offener-haushalt took 2.8396542072296143s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.1961669921875e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.2756619453430176s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 3.0994415283203125e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.075599670410156e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 7.62939453125e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.988675117492676s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 0.37774085998535156s
Availability | VoID file availability check for business.data.gov.uk took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.26900792121887207s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.028498172760009766s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.0008862018585205078s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 5.888938903808594e-05s
Believability | Calculation of trust value for business.data.gov.uk took 9.298324584960938e-06s
INFO | --- Analysis for business-data-gov-uk took 2.9754645824432373s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 1.0116708278656006s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.2827579975128174s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 4.6253204345703125e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 9.5367431640625e-06s
INFO | --- Analysis for BVMC took 5.281042814254761s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.0531158447265625e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.2723371982574463s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.02019667625427246s
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.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.62939453125e-06s
INFO | --- Analysis for cabbage took 2.939150810241699s
Availability | SPARQL endpoint availability check for cablegate took 1.545708417892456s
Availability | VoID file availability check for cablegate took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for cablegate took 0.2711613178253174s
Reputation | Calculation of the PageRank for cablegate took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for cablegate took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.890296936035156e-05s
Believability | Calculation of trust value for cablegate took 7.3909759521484375e-06s
INFO | --- Analysis for cablegate took 16.303716897964478s
Availability | SPARQL endpoint availability check for Calames took 4.315376281738281e-05s
Availability | VoID file availability check for Calames took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Calames took 0.27898454666137695s
Reputation | Calculation of the PageRank for Calames took 0.02037978172302246s
Interlinking | Calculation of Degree of Connection for Calames took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Calames took 3.2901763916015625e-05s
Believability | Calculation of trust value for Calames took 7.152557373046875e-06s
INFO | --- Analysis for calames took 4.64151406288147s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.5623414516448975s
Availability | VoID file availability check for CaLiGraph took 0.0002617835998535156s
Extra | Recovery of all triples for CaLiGraph took 1.2781484127044678s
Performance | Total latancy measurement for CaLiGraph took 1.2671363353729248s
Amount of data | Number of triples check for CaLiGraph took 12.61719799041748s
Interoperability | New terms check for CaLiGraph took 1.899742603302002s
Versatility | Languages check for CaLiGraph took 60.36042523384094s
Interpretability | Number of blank nodes check for CaLiGraph took 0.25852084159851074s
Security | Check HTTPS for CaLiGraph took 0.13994312286376953s
Interpretability | RDF structures check for CaLiGraph took 0.282146692276001s
Versatility | Serialization formats check for CaLiGraph took 0.31005239486694336s
Availability | RDF dump link check for CaLiGraph took 0.2581825256347656s
License | MR license check for CaLiGraph took 0.31291699409484863s
License | HR license check for CaLiGraph took 60.32188296318054s
Amount of data | Number of property check for CaLiGraph took 0.33231592178344727s
Understandability | Number of label check for CaLiGraph took 3.3558263778686523s
Understandability | URI regex check for CaLiGraph took 0.6117227077484131s
Understandability | Vocabs check for CaLiGraph took 0.31748127937316895s
Verifiability | Authors check for CaLiGraph took 0.2637917995452881s
Verifiability | Publishers check for CaLiGraph took 0.27301716804504395s
Performance | Throughput check for CaLiGraph took 11.393200635910034s
Amount of data | Check the number of entities for CaLiGraph took 0.016969919204711914s
Verifiability | Contribs. check for CaLiGraph took 0.40505194664001465s
Interlinking | sameAs chians check for CaLiGraph took 0.7486064434051514s
Interlinking | skos check for CaLiGraph took 0.3566253185272217s
Interlinking | skos check for CaLiGraph took 0.2670555114746094s
Timeliness | dataset update frequency check for CaLiGraph took 0.33260035514831543s
Currency | Creation date check for CaLiGraph took 0.6592223644256592s
Currency | Modification date check for CaLiGraph took 0.5167150497436523s
Rep.Conc. | URIs length for CaLiGraph took 61.01837873458862s
Interoperability | New vocabularies check for CaLiGraph took 4.291534423828125e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.25931382179260254s
Accuracy | Check Functional Property for CaLiGraph took 0.2650108337402344s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.2841763496398926s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.5966160297393799s
Accuracy | Check White space in annotation for CaLiGraph took 0.026565074920654297s
Accuracy | Check Datatype consistency for CaLiGraph took 0.05079078674316406s
Consistency | Disjoint class check for CaLiGraph took 0.26820993423461914s
Consistency | Check Misplaced properties for CaLiGraph took 60.933722257614136s
Consistency | Misplaced classes for CaLiGraph took 0.5310008525848389s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9969022274017334s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2663140296936035s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.62378168106079s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.03358912467956543s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.5376057624816895s
Security | Sign check for CaLiGraph took 0.3275423049926758s
Availability | Check URIs Dereferenciability for CaLiGraph took 11.864325523376465s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.46288585662841797s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 3.838539123535156e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.6689300537109375e-06s
Believability | Calculation of trust value for CaLiGraph took 6.67572021484375e-06s
INFO | --- Analysis for CaLiGraph took 1496.0407948493958s
Availability | SPARQL endpoint availability check for CaLiGraph took 0.2573065757751465s
Availability | VoID file availability check for CaLiGraph took 0.0006701946258544922s
Extra | Recovery of all triples for CaLiGraph took 1.225928783416748s
Performance | Total latancy measurement for CaLiGraph took 1.3393452167510986s
Amount of data | Number of triples check for CaLiGraph took 12.501385688781738s
Interoperability | New terms check for CaLiGraph took 1.9395568370819092s
Versatility | Languages check for CaLiGraph took 60.337210178375244s
Interpretability | Number of blank nodes check for CaLiGraph took 0.28938746452331543s
Security | Check HTTPS for CaLiGraph took 0.1285862922668457s
Interpretability | RDF structures check for CaLiGraph took 0.2988014221191406s
Versatility | Serialization formats check for CaLiGraph took 0.2644834518432617s
Availability | RDF dump link check for CaLiGraph took 0.2752206325531006s
License | MR license check for CaLiGraph took 0.29304027557373047s
License | HR license check for CaLiGraph took 60.357733488082886s
Amount of data | Number of property check for CaLiGraph took 0.25316643714904785s
Understandability | Number of label check for CaLiGraph took 3.1023108959198s
Understandability | URI regex check for CaLiGraph took 0.5292353630065918s
Understandability | Vocabs check for CaLiGraph took 0.28104472160339355s
Verifiability | Authors check for CaLiGraph took 0.27667760848999023s
Verifiability | Publishers check for CaLiGraph took 0.2795267105102539s
Performance | Throughput check for CaLiGraph took 11.495710611343384s
Amount of data | Check the number of entities for CaLiGraph took 0.01716160774230957s
Verifiability | Contribs. check for CaLiGraph took 0.2494947910308838s
Interlinking | sameAs chians check for CaLiGraph took 0.7016441822052002s
Interlinking | skos check for CaLiGraph took 0.2530851364135742s
Interlinking | skos check for CaLiGraph took 0.23924803733825684s
Timeliness | dataset update frequency check for CaLiGraph took 0.265333890914917s
Currency | Creation date check for CaLiGraph took 0.5035080909729004s
Currency | Modification date check for CaLiGraph took 0.5022072792053223s
Rep.Conc. | URIs length for CaLiGraph took 60.98347568511963s
Interoperability | New vocabularies check for CaLiGraph took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for CaLiGraph took 0.2936980724334717s
Accuracy | Check Functional Property for CaLiGraph took 0.270505428314209s
Accuracy | Check Inverse Functional Property for CaLiGraph took 0.256882905960083s
Accuracy | Check Empty annotation labels for CaLiGraph took 0.6354711055755615s
Accuracy | Check White space in annotation for CaLiGraph took 0.026383638381958008s
Accuracy | Check Datatype consistency for CaLiGraph took 0.048250436782836914s
Consistency | Disjoint class check for CaLiGraph took 0.3733031749725342s
Consistency | Check Misplaced properties for CaLiGraph took 61.023478746414185s
Consistency | Misplaced classes for CaLiGraph took 0.5977988243103027s
Consistency | Check Ontology hijacking for CaLiGraph took 1.9809472560882568s
Consistency | Check Invalid usage of undefined classes for CaLiGraph took 1.2936089038848877s
Consistency | Check Invalid usage of undefined properties for CaLiGraph took 61.577091455459595s
Conciseness | Check Extensional conciseness for CaLiGraph took 0.02935338020324707s
Conciseness | Check Intensional conciseness for CaLiGraph took 0.5002992153167725s
Security | Sign check for CaLiGraph took 0.3253974914550781s
Availability | Check URIs Dereferenciability for CaLiGraph took 10.198751449584961s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.3798985481262207s
Reputation | Calculation of the PageRank for CaLiGraph took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for CaLiGraph took 1.430511474609375e-06s
Believability | Calculation of trust value for CaLiGraph took 6.9141387939453125e-06s
INFO | --- Analysis for caligraph took 1493.0451350212097s
Availability | SPARQL endpoint availability check for can-link took 4.267692565917969e-05s
Availability | VoID file availability check for can-link took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for can-link took 0.7031338214874268s
Reputation | Calculation of the PageRank for can-link took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for can-link took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for can-link took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for can-link took 3.123283386230469e-05s
Believability | Calculation of trust value for can-link took 6.4373016357421875e-06s
INFO | --- Analysis for can-link took 5.5297393798828125s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 0.0867471694946289s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.28347182273864746s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020119428634643555s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for cap-italy-rdf took 3.028575897216797s
Availability | SPARQL endpoint availability check for person took 4.4345855712890625e-05s
Availability | VoID file availability check for person took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for person took 0.2973904609680176s
Reputation | Calculation of the PageRank for person took 0.02019214630126953s
Interlinking | Calculation of Degree of Connection for person took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for person took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for person took 2.9087066650390625e-05s
Believability | Calculation of trust value for person took 6.67572021484375e-06s
INFO | --- Analysis for card took 3.2823917865753174s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.220008850097656e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2690858840942383s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.814697265625e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 7.152557373046875e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.9232230186462402s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.076957702636719e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.2697889804840088s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.0040740966796875e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 6.9141387939453125e-06s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 3.321256399154663s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 0.7651922702789307s
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 116.80963969230652s
Performance | Total latancy measurement for Norway catch records dataset @PSNC took 0.9290180206298828s
Amount of data | Number of triples check for Norway catch records dataset @PSNC took 8.6903076171875s
Interoperability | New terms check for Norway catch records dataset @PSNC took 13.60011100769043s
Versatility | Languages check for Norway catch records dataset @PSNC took 300.1910808086395s
Interpretability | Number of blank nodes check for Norway catch records dataset @PSNC took 3.062673807144165s
Interpretability | RDF structures check for Norway catch records dataset @PSNC took 0.2182466983795166s
Versatility | Serialization formats check for Norway catch records dataset @PSNC took 8.510435342788696s
Availability | RDF dump link check for Norway catch records dataset @PSNC took 0.3227667808532715s
License | MR license check for Norway catch records dataset @PSNC took 0.519251823425293s
License | HR license check for Norway catch records dataset @PSNC took 300.23523783683777s
Amount of data | Number of property check for Norway catch records dataset @PSNC took 0.31583142280578613s
Understandability | Number of label check for Norway catch records dataset @PSNC took 2.437861442565918s
Understandability | URI regex check for Norway catch records dataset @PSNC took 0.7942659854888916s
Understandability | Vocabs check for Norway catch records dataset @PSNC took 0.40447068214416504s
Verifiability | Authors check for Norway catch records dataset @PSNC took 0.19729852676391602s
Verifiability | Publishers check for Norway catch records dataset @PSNC took 0.24056601524353027s
Performance | Throughput check for Norway catch records dataset @PSNC took 11.520395755767822s
Amount of data | Check the number of entities for Norway catch records dataset @PSNC took 7.486343383789062e-05s
Verifiability | Contribs. check for Norway catch records dataset @PSNC took 0.19630694389343262s
Interlinking | sameAs chians check for Norway catch records dataset @PSNC took 0.182600736618042s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.44889068603515625s
Interlinking | skos check for Norway catch records dataset @PSNC took 0.4408078193664551s
Timeliness | dataset update frequency check for Norway catch records dataset @PSNC took 3.944275379180908s
Currency | Creation date check for Norway catch records dataset @PSNC took 0.45821428298950195s
Currency | Modification date check for Norway catch records dataset @PSNC took 0.21951794624328613s
Rep.Conc. | URIs length for Norway catch records dataset @PSNC took 145.00889229774475s
Interoperability | New vocabularies check for Norway catch records dataset @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Norway catch records dataset @PSNC took 0.19553637504577637s
Accuracy | Check Functional Property for Norway catch records dataset @PSNC took 0.2903609275817871s
Accuracy | Check Inverse Functional Property for Norway catch records dataset @PSNC took 0.2582895755767822s
Accuracy | Check Empty annotation labels for Norway catch records dataset @PSNC took 41.572678327560425s
Accuracy | Check White space in annotation for Norway catch records dataset @PSNC took 2.6915996074676514s
Accuracy | Check Datatype consistency for Norway catch records dataset @PSNC took 2.598586320877075s
Consistency | Disjoint class check for Norway catch records dataset @PSNC took 0.18007612228393555s
Consistency | Check Misplaced properties for Norway catch records dataset @PSNC took 89.47048997879028s
Consistency | Misplaced classes for Norway catch records dataset @PSNC took 8.273788452148438s
Consistency | Check Ontology hijacking for Norway catch records dataset @PSNC took 34.392301082611084s
Consistency | Check Invalid usage of undefined classes for Norway catch records dataset @PSNC took 1.3325517177581787s
Consistency | Check Invalid usage of undefined properties for Norway catch records dataset @PSNC took 86.00320363044739s
Conciseness | Check Extensional conciseness for Norway catch records dataset @PSNC took 2.8028252124786377s
Conciseness | Check Intensional conciseness for Norway catch records dataset @PSNC took 0.5937769412994385s
Security | Sign check for Norway catch records dataset @PSNC took 0.6264927387237549s
Availability | Check URIs Dereferenciability for Norway catch records dataset @PSNC took 9.88405156135559s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.4744882583618164s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02112269401550293s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.504753112792969e-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 7.867813110351562e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2255.33553981781s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.863739013671875e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.6671710014343262s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.021054506301879883s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010204315185546875s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.059906005859375e-06s
INFO | --- Analysis for ce4r took 42.41504502296448s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.48374104499816895s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0003421306610107422s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.280381679534912s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.750514030456543s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.26345300674438477s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.5942153930664062s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.13773488998413s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15073156356811523s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2699615955352783s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1452624797821045s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.13278889656066895s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20311570167541504s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3009819984436035s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1658167839050293s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23819255828857422s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2958354949951172s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14866161346435547s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.20115327835083008s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.14242815971374512s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.547699928283691s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.271766662597656e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16321182250976562s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2053241729736328s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2990262508392334s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18537449836730957s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.13872241973876953s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.351168155670166s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.32896876335144043s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 1.9544508457183838s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21277689933776855s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.16604971885681152s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.19290423393249512s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.9674890041351318s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.02913689613342285s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.03020000457763672s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18947815895080566s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.198568344116211s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 1.9234669208526611s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3108470439910889s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.493741750717163s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.0331265926361084s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.18944001197814941s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1510143280029297s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 1904.337574005127s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.4143240451812744s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.8160552978515625e-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 7.3909759521484375e-06s
INFO | --- Analysis for ceo took 2028.8299505710602s
Availability | SPARQL endpoint availability check for Charging Stations took 4.3392181396484375e-05s
Availability | VoID file availability check for Charging Stations took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.2590155601501465s
Reputation | Calculation of the PageRank for Charging Stations took 0.020141124725341797s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.2901763916015625e-05s
Believability | Calculation of trust value for Charging Stations took 1.5497207641601562e-05s
INFO | --- Analysis for charging-stations took 4.329293251037598s
Availability | SPARQL endpoint availability check for Chat Game corpus took 5.459785461425781e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.262631893157959s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020833492279052734s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.4809112548828125e-05s
Believability | Calculation of trust value for Chat Game corpus took 7.152557373046875e-06s
INFO | --- Analysis for chat-game-corpus took 13.45197606086731s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 7.557868957519531e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.2622528076171875s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.4332275390625e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 7.62939453125e-06s
INFO | --- Analysis for chebi took 3.3391964435577393s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.315376281738281e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.0007624626159667969s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.2945699691772461s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.1021575927734375e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 6.67572021484375e-06s
INFO | --- Analysis for chem2bio2rdf took 135.19748997688293s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 0.5904090404510498s
Availability | VoID file availability check for ChEMBL RDF took 0.0005710124969482422s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.2653830051422119s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 5.030632019042969e-05s
Believability | Calculation of trust value for ChEMBL RDF took 6.9141387939453125e-06s
INFO | --- Analysis for chembl-rdf took 4.0679590702056885s
Availability | SPARQL endpoint availability check for chemdb  dataset took 1.742154836654663s
Availability | VoID file availability check for chemdb  dataset took 0.00025916099548339844s
Extra | Recovery of all triples for chemdb  dataset took 29.175424337387085s
Performance | Total latancy measurement for chemdb  dataset took 2.536355495452881s
Amount of data | Number of triples check for chemdb  dataset took 0.5501053333282471s
Interoperability | New terms check for chemdb  dataset took 10.691929340362549s
Versatility | Languages check for chemdb  dataset took 28.801838159561157s
Interpretability | Number of blank nodes check for chemdb  dataset took 0.5341002941131592s
Interpretability | RDF structures check for chemdb  dataset took 0.5331690311431885s
Versatility | Serialization formats check for chemdb  dataset took 1.4851148128509521s
Availability | RDF dump link check for chemdb  dataset took 0.6276407241821289s
License | MR license check for chemdb  dataset took 2.3477351665496826s
License | HR license check for chemdb  dataset took 3.911120891571045s
Amount of data | Number of property check for chemdb  dataset took 0.5319416522979736s
Understandability | Number of label check for chemdb  dataset took 2.350295305252075s
Understandability | URI regex check for chemdb  dataset took 1.9636352062225342s
Understandability | Vocabs check for chemdb  dataset took 0.806934118270874s
Verifiability | Authors check for chemdb  dataset took 0.8101832866668701s
Verifiability | Publishers check for chemdb  dataset took 0.8193886280059814s
Performance | Throughput check for chemdb  dataset took 13.470398664474487s
Amount of data | Check the number of entities for chemdb  dataset took 6.842613220214844e-05s
Verifiability | Contribs. check for chemdb  dataset took 0.8044784069061279s
Interlinking | sameAs chians check for chemdb  dataset took 0.8439688682556152s
Interlinking | skos check for chemdb  dataset took 2.1089797019958496s
Interlinking | skos check for chemdb  dataset took 0.49691152572631836s
Timeliness | dataset update frequency check for chemdb  dataset took 1.1171491146087646s
Currency | Creation date check for chemdb  dataset took 1.3698678016662598s
Currency | Modification date check for chemdb  dataset took 1.0334837436676025s
Rep.Conc. | URIs length for chemdb  dataset took 6.621077299118042s
Interoperability | New vocabularies check for chemdb  dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb  dataset took 0.5195872783660889s
Accuracy | Check Functional Property for chemdb  dataset took 0.8060059547424316s
Accuracy | Check Inverse Functional Property for chemdb  dataset took 0.7826364040374756s
Accuracy | Check Empty annotation labels for chemdb  dataset took 4.356695652008057s
Accuracy | Check White space in annotation for chemdb  dataset took 0.030350208282470703s
Accuracy | Check Datatype consistency for chemdb  dataset took 0.032952070236206055s
Consistency | Disjoint class check for chemdb  dataset took 0.8322103023529053s
Consistency | Check Misplaced properties for chemdb  dataset took 2.2468276023864746s
Consistency | Misplaced classes for chemdb  dataset took 0.6103911399841309s
Consistency | Check Ontology hijacking for chemdb  dataset took 16.185720682144165s
Consistency | Check Invalid usage of undefined classes for chemdb  dataset took 1.259105920791626s
Consistency | Check Invalid usage of undefined properties for chemdb  dataset took 1.953850507736206s
Conciseness | Check Extensional conciseness for chemdb  dataset took 0.03181338310241699s
Conciseness | Check Intensional conciseness for chemdb  dataset took 0.5354199409484863s
Security | Sign check for chemdb  dataset took 2.025139331817627s
Availability | Check URIs Dereferenciability for chemdb  dataset took 2745.4263083934784s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 1.540846586227417s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.02093648910522461s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.534027099609375e-05s
Interoperability | Check the re-using of existing vocabs for chemdb  dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb  dataset took 7.867813110351562e-06s
INFO | --- Analysis for chemdb-basicInfo took 3911.3003652095795s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 0.5336177349090576s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0002601146697998047s
Extra | Recovery of all triples for chemdb estimated properties dataset took 40.011614084243774s
Performance | Total latancy measurement for chemdb estimated properties dataset took 2.5299553871154785s
Amount of data | Number of triples check for chemdb estimated properties dataset took 0.5523858070373535s
Interoperability | New terms check for chemdb estimated properties dataset took 10.041483402252197s
Versatility | Languages check for chemdb estimated properties dataset took 28.002398014068604s
Interpretability | Number of blank nodes check for chemdb estimated properties dataset took 0.5214686393737793s
Interpretability | RDF structures check for chemdb estimated properties dataset took 0.5339245796203613s
Versatility | Serialization formats check for chemdb estimated properties dataset took 1.506944179534912s
Availability | RDF dump link check for chemdb estimated properties dataset took 0.847423791885376s
License | MR license check for chemdb estimated properties dataset took 2.883096933364868s
License | HR license check for chemdb estimated properties dataset took 4.067987442016602s
Amount of data | Number of property check for chemdb estimated properties dataset took 0.5240838527679443s
Understandability | Number of label check for chemdb estimated properties dataset took 5.749303340911865s
Understandability | URI regex check for chemdb estimated properties dataset took 1.9676892757415771s
Understandability | Vocabs check for chemdb estimated properties dataset took 0.8279352188110352s
Verifiability | Authors check for chemdb estimated properties dataset took 1.152963638305664s
Verifiability | Publishers check for chemdb estimated properties dataset took 0.8117563724517822s
Performance | Throughput check for chemdb estimated properties dataset took 13.021641969680786s
Amount of data | Check the number of entities for chemdb estimated properties dataset took 7.963180541992188e-05s
Verifiability | Contribs. check for chemdb estimated properties dataset took 0.8385775089263916s
Interlinking | sameAs chians check for chemdb estimated properties dataset took 0.9615404605865479s
Interlinking | skos check for chemdb estimated properties dataset took 2.088747024536133s
Interlinking | skos check for chemdb estimated properties dataset took 0.4866352081298828s
Timeliness | dataset update frequency check for chemdb estimated properties dataset took 0.9439444541931152s
Currency | Creation date check for chemdb estimated properties dataset took 1.3370938301086426s
Currency | Modification date check for chemdb estimated properties dataset took 1.036113977432251s
Rep.Conc. | URIs length for chemdb estimated properties dataset took 11.410090208053589s
Interoperability | New vocabularies check for chemdb estimated properties dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb estimated properties dataset took 0.4915578365325928s
Accuracy | Check Functional Property for chemdb estimated properties dataset took 0.8164405822753906s
Accuracy | Check Inverse Functional Property for chemdb estimated properties dataset took 0.7850449085235596s
Accuracy | Check Empty annotation labels for chemdb estimated properties dataset took 9.370708227157593s
Accuracy | Check White space in annotation for chemdb estimated properties dataset took 0.030648469924926758s
Accuracy | Check Datatype consistency for chemdb estimated properties dataset took 0.03316187858581543s
Consistency | Disjoint class check for chemdb estimated properties dataset took 0.8085098266601562s
Consistency | Check Misplaced properties for chemdb estimated properties dataset took 1.2181730270385742s
Consistency | Misplaced classes for chemdb estimated properties dataset took 0.6192059516906738s
Consistency | Check Ontology hijacking for chemdb estimated properties dataset took 13.717792987823486s
Consistency | Check Invalid usage of undefined classes for chemdb estimated properties dataset took 1.2661707401275635s
Consistency | Check Invalid usage of undefined properties for chemdb estimated properties dataset took 3.2089221477508545s
Conciseness | Check Extensional conciseness for chemdb estimated properties dataset took 0.03294181823730469s
Conciseness | Check Intensional conciseness for chemdb estimated properties dataset took 0.5318284034729004s
Security | Sign check for chemdb estimated properties dataset took 3.2827861309051514s
Availability | Check URIs Dereferenciability for chemdb estimated properties dataset took 2786.595582008362s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.6210596561431885s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.02082371711730957s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 5.078315734863281e-05s
Interoperability | Check the re-using of existing vocabs for chemdb estimated properties dataset took 1.1920928955078125e-06s
Believability | Calculation of trust value for chemdb estimated properties dataset took 7.3909759521484375e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 3913.6636333465576s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 0.5366291999816895s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002598762512207031s
Extra | Recovery of all triples for chemdb phase transition dataset took 40.896146059036255s
Performance | Total latancy measurement for chemdb phase transition dataset took 2.4712729454040527s
Amount of data | Number of triples check for chemdb phase transition dataset took 0.556049108505249s
Interoperability | New terms check for chemdb phase transition dataset took 5.541296482086182s
Versatility | Languages check for chemdb phase transition dataset took 27.96614098548889s
Interpretability | Number of blank nodes check for chemdb phase transition dataset took 0.5345160961151123s
Interpretability | RDF structures check for chemdb phase transition dataset took 0.6669623851776123s
Versatility | Serialization formats check for chemdb phase transition dataset took 1.614762783050537s
Availability | RDF dump link check for chemdb phase transition dataset took 0.8439140319824219s
License | MR license check for chemdb phase transition dataset took 3.1299538612365723s
License | HR license check for chemdb phase transition dataset took 4.2625837326049805s
Amount of data | Number of property check for chemdb phase transition dataset took 0.5433874130249023s
Understandability | Number of label check for chemdb phase transition dataset took 6.174009561538696s
Understandability | URI regex check for chemdb phase transition dataset took 2.048032760620117s
Understandability | Vocabs check for chemdb phase transition dataset took 0.8395175933837891s
Verifiability | Authors check for chemdb phase transition dataset took 1.2104029655456543s
Verifiability | Publishers check for chemdb phase transition dataset took 0.8650417327880859s
Performance | Throughput check for chemdb phase transition dataset took 13.727108478546143s
Amount of data | Check the number of entities for chemdb phase transition dataset took 7.2479248046875e-05s
Verifiability | Contribs. check for chemdb phase transition dataset took 0.867542028427124s
Interlinking | sameAs chians check for chemdb phase transition dataset took 1.064767599105835s
Interlinking | skos check for chemdb phase transition dataset took 2.207707166671753s
Interlinking | skos check for chemdb phase transition dataset took 0.5084512233734131s
Timeliness | dataset update frequency check for chemdb phase transition dataset took 1.2569515705108643s
Currency | Creation date check for chemdb phase transition dataset took 1.404939889907837s
Currency | Modification date check for chemdb phase transition dataset took 1.0416982173919678s
Rep.Conc. | URIs length for chemdb phase transition dataset took 12.773682832717896s
Interoperability | New vocabularies check for chemdb phase transition dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for chemdb phase transition dataset took 0.4874305725097656s
Accuracy | Check Functional Property for chemdb phase transition dataset took 0.786247968673706s
Accuracy | Check Inverse Functional Property for chemdb phase transition dataset took 0.7851638793945312s
Accuracy | Check Empty annotation labels for chemdb phase transition dataset took 12.141360998153687s
Accuracy | Check White space in annotation for chemdb phase transition dataset took 0.030812978744506836s
Accuracy | Check Datatype consistency for chemdb phase transition dataset took 0.03343605995178223s
Consistency | Disjoint class check for chemdb phase transition dataset took 0.8477787971496582s
Consistency | Check Misplaced properties for chemdb phase transition dataset took 2.440600633621216s
Consistency | Misplaced classes for chemdb phase transition dataset took 0.6210205554962158s
Consistency | Check Ontology hijacking for chemdb phase transition dataset took 7.735280752182007s
Consistency | Check Invalid usage of undefined classes for chemdb phase transition dataset took 1.2455391883850098s
Consistency | Check Invalid usage of undefined properties for chemdb phase transition dataset took 2.7089548110961914s
Conciseness | Check Extensional conciseness for chemdb phase transition dataset took 0.03229784965515137s
Conciseness | Check Intensional conciseness for chemdb phase transition dataset took 0.5231761932373047s
Security | Sign check for chemdb phase transition dataset took 1.9660632610321045s
Availability | Check URIs Dereferenciability for chemdb phase transition dataset took 2757.9099271297455s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 1.6093683242797852s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020985841751098633s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 5.793571472167969e-05s
Interoperability | Check the re-using of existing vocabs for chemdb phase transition dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for chemdb phase transition dataset took 9.5367431640625e-06s
INFO | --- Analysis for chemdb-phaseTransition took 3868.4340279102325s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 0.5180814266204834s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00029015541076660156s
Extra | Recovery of all triples for chemdb thermochemistry dataset took 39.978529930114746s
Performance | Total latancy measurement for chemdb thermochemistry dataset took 2.516845464706421s
Amount of data | Number of triples check for chemdb thermochemistry dataset took 0.5476481914520264s
Interoperability | New terms check for chemdb thermochemistry dataset took 11.183721780776978s
Versatility | Languages check for chemdb thermochemistry dataset took 26.794758558273315s
Interpretability | Number of blank nodes check for chemdb thermochemistry dataset took 0.8375093936920166s
Interpretability | RDF structures check for chemdb thermochemistry dataset took 0.8316798210144043s
Versatility | Serialization formats check for chemdb thermochemistry dataset took 1.572455644607544s
Availability | RDF dump link check for chemdb thermochemistry dataset took 0.6338434219360352s
License | MR license check for chemdb thermochemistry dataset took 2.787200450897217s
License | HR license check for chemdb thermochemistry dataset took 4.055318117141724s
Amount of data | Number of property check for chemdb thermochemistry dataset took 0.523369550704956s
Understandability | Number of label check for chemdb thermochemistry dataset took 5.369739532470703s
Understandability | URI regex check for chemdb thermochemistry dataset took 2.001601219177246s
Understandability | Vocabs check for chemdb thermochemistry dataset took 0.8355669975280762s
Verifiability | Authors check for chemdb thermochemistry dataset took 1.0130317211151123s
Verifiability | Publishers check for chemdb thermochemistry dataset took 0.8099706172943115s
Performance | Throughput check for chemdb thermochemistry dataset took 13.443280696868896s
Amount of data | Check the number of entities for chemdb thermochemistry dataset took 9.036064147949219e-05s
Verifiability | Contribs. check for chemdb thermochemistry dataset took 0.8308334350585938s
Interlinking | sameAs chians check for chemdb thermochemistry dataset took 1.1530029773712158s
Interlinking | skos check for chemdb thermochemistry dataset took 2.0141122341156006s
Interlinking | skos check for chemdb thermochemistry dataset took 0.5097391605377197s
Timeliness | dataset update frequency check for chemdb thermochemistry dataset took 1.1821928024291992s
Currency | Creation date check for chemdb thermochemistry dataset took 1.3304977416992188s
Currency | Modification date check for chemdb thermochemistry dataset took 1.0202174186706543s
Rep.Conc. | URIs length for chemdb thermochemistry dataset took 11.866206169128418s
Interoperability | New vocabularies check for chemdb thermochemistry dataset took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for chemdb thermochemistry dataset took 0.4990518093109131s
Accuracy | Check Functional Property for chemdb thermochemistry dataset took 0.8140575885772705s
Accuracy | Check Inverse Functional Property for chemdb thermochemistry dataset took 0.8023054599761963s
Accuracy | Check Empty annotation labels for chemdb thermochemistry dataset took 13.985860347747803s
Accuracy | Check White space in annotation for chemdb thermochemistry dataset took 0.030745506286621094s
Accuracy | Check Datatype consistency for chemdb thermochemistry dataset took 0.03289961814880371s
Consistency | Disjoint class check for chemdb thermochemistry dataset took 0.7858898639678955s
Consistency | Check Misplaced properties for chemdb thermochemistry dataset took 2.670440435409546s
Consistency | Misplaced classes for chemdb thermochemistry dataset took 0.6046154499053955s
Consistency | Check Ontology hijacking for chemdb thermochemistry dataset took 8.802939891815186s
Consistency | Check Invalid usage of undefined classes for chemdb thermochemistry dataset took 1.2518706321716309s
Consistency | Check Invalid usage of undefined properties for chemdb thermochemistry dataset took 1.9627718925476074s
Conciseness | Check Extensional conciseness for chemdb thermochemistry dataset took 0.03199291229248047s
Conciseness | Check Intensional conciseness for chemdb thermochemistry dataset took 0.5140020847320557s
Security | Sign check for chemdb thermochemistry dataset took 1.9707839488983154s
Availability | Check URIs Dereferenciability for chemdb thermochemistry dataset took 2770.64976978302s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.7465977668762207s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021270751953125s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for chemdb thermochemistry dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 7.867813110351562e-06s
INFO | --- Analysis for chemdb-thermochemistry took 3885.1248891353607s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.482269287109375e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.7091145515441895s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 5.0067901611328125e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.152557373046875e-06s
INFO | --- Analysis for chempedia-rdf took 12.142992973327637s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.291534423828125e-05s
Availability | VoID file availability check for Chiman Maru took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.27831006050109863s
Reputation | Calculation of the PageRank for Chiman Maru took 0.02021169662475586s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 2.86102294921875e-05s
Believability | Calculation of trust value for Chiman Maru took 6.67572021484375e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.823972463607788s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.5305383205414s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0005970001220703125s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.3459286689758301s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.020650148391723633s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.337860107421875e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 797.5564620494843s
Availability | SPARQL endpoint availability check for Chronicling America took 4.6253204345703125e-05s
Availability | VoID file availability check for Chronicling America took 0.0003542900085449219s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.2514941692352295s
Reputation | Calculation of the PageRank for Chronicling America took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Chronicling America took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 9.965896606445312e-05s
Believability | Calculation of trust value for Chronicling America took 6.9141387939453125e-06s
INFO | --- Analysis for chronicling-america took 8.287970304489136s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.8202297687530518s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0003662109375s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 87.94176459312439s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.609755039215088s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.7179310321807861s
Interoperability | New terms check for Cultural Heritage Thesaurus took 1.9091074466705322s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.86000394821167s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.6203422546386719s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.29996204376220703s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.28846311569213867s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.910398721694946s
License | MR license check for Cultural Heritage Thesaurus took 0.3113570213317871s
License | HR license check for Cultural Heritage Thesaurus took 0.44080305099487305s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.26784300804138184s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.37762951850891113s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5769612789154053s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.313631534576416s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2656841278076172s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.31896305084228516s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.977081537246704s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 8.749961853027344e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.31116366386413574s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.37126898765563965s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.33537840843200684s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.27375173568725586s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.29775571823120117s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6152238845825195s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5971925258636475s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 9.880143880844116s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 8.475407838821411s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.3423466682434082s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.28564906120300293s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.3129763603210449s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 3.4246177673339844s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22398114204406738s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.3067033290863037s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.1531195640563965s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.28128862380981445s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 5.630989074707031s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.115628957748413s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00016236305236816406s
Security | Sign check for Cultural Heritage Thesaurus took 0.27246713638305664s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 285.69795274734497s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 1.4537222385406494s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.1674518585205078s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0008914470672607422s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 0.00012183189392089844s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 2.4937591552734375s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for cht took 471.7933027744293s
Availability | SPARQL endpoint availability check for ciard-ring took 4.649162292480469e-05s
Availability | VoID file availability check for ciard-ring took 0.0006110668182373047s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.7084817886352539s
Reputation | Calculation of the PageRank for ciard-ring took 0.04275059700012207s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0010271072387695312s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 6.604194641113281e-05s
Believability | Calculation of trust value for ciard-ring took 7.3909759521484375e-06s
INFO | --- Analysis for ciard-ring took 7.45667839050293s
Availability | SPARQL endpoint availability check for Cine Figure took 4.458427429199219e-05s
Availability | VoID file availability check for Cine Figure took 0.0006961822509765625s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.27585840225219727s
Reputation | Calculation of the PageRank for Cine Figure took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.7206878662109375e-05s
Believability | Calculation of trust value for Cine Figure took 5.9604644775390625e-06s
INFO | --- Analysis for Cine_Figure took 2.9279768466949463s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 21.286622047424316s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0006010532379150391s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.6758198738098145s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 5.626678466796875e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 175.98724102973938s
Availability | SPARQL endpoint availability check for CIPFA took 4.673004150390625e-05s
Availability | VoID file availability check for CIPFA took 0.00034546852111816406s
Completeness | Calculation of interlinking completeness for CIPFA took 0.2849898338317871s
Reputation | Calculation of the PageRank for CIPFA took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.2901763916015625e-05s
Believability | Calculation of trust value for CIPFA took 5.0067901611328125e-06s
INFO | --- Analysis for cipfa took 3.265533924102783s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 60.042402029037476s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0006768703460693359s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.28018712997436523s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 3.457069396972656e-05s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0007653236389160156s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.0004112720489501953s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 7.62939453125e-06s
INFO | --- Analysis for ckan took 263.6196937561035s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6183161735534668s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007107257843017578s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.6971590518951416s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for CLaSSES took 4.956862926483154s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 6.794929504394531e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2667860984802246s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.02125859260559082s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 3.0279159545898438e-05s
Believability | Calculation of trust value for Temples of the Classical World took 7.152557373046875e-06s
INFO | --- Analysis for classical_temples took 3.64866304397583s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 1.9359941482543945s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.2521219253540039s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 8.416175842285156e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 5.4836273193359375e-06s
INFO | --- Analysis for clean-energy-data-reegle took 13.658640623092651s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.220008850097656e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.2592170238494873s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.020266056060791016s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.724761962890625e-05s
Believability | Calculation of trust value for CLLD-afbo took 6.9141387939453125e-06s
INFO | --- Analysis for clld-afbo took 3.4461236000061035s
Availability | SPARQL endpoint availability check for CLLD-APICS took 0.00015020370483398438s
Availability | VoID file availability check for CLLD-APICS took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2832372188568115s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.700920104980469e-05s
Believability | Calculation of trust value for CLLD-APICS took 7.152557373046875e-06s
INFO | --- Analysis for clld-apics took 3.4831180572509766s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 4.410743713378906e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.2737257480621338s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020756959915161133s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 4.291534423828125e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 7.3909759521484375e-06s
INFO | --- Analysis for clld-ewave took 3.462953567504883s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 5.555152893066406e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.001455545425415039s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.26217150688171387s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00010228157043457031s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 7.152557373046875e-06s
INFO | --- Analysis for clld-glottolog took 3.4455435276031494s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 4.315376281738281e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0005674362182617188s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.7066361904144287s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 9.679794311523438e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.67572021484375e-06s
INFO | --- Analysis for clld-phoible took 3.9408228397369385s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 4.220008850097656e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.27136802673339844s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 8.440017700195312e-05s
Believability | Calculation of trust value for CLLD-SAILS took 7.867813110351562e-06s
INFO | --- Analysis for clld-sails took 3.7125964164733887s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.38690185546875e-05s
Availability | VoID file availability check for CLLD-WALS took 0.0005865097045898438s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.280759334564209s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.106231689453125e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.2874603271484375e-05s
INFO | --- Analysis for clld-wals took 3.633556365966797s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 4.458427429199219e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.2712266445159912s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020785808563232422s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 8.678436279296875e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.049041748046875e-05s
INFO | --- Analysis for clld-wold took 3.477810859680176s
Availability | SPARQL endpoint availability check for COD inventory took 4.410743713378906e-05s
Availability | VoID file availability check for COD inventory took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for COD inventory took 0.26423096656799316s
Reputation | Calculation of the PageRank for COD inventory took 0.020939111709594727s
Interlinking | Calculation of Degree of Connection for COD inventory took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COD inventory took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for COD inventory took 3.4332275390625e-05s
Believability | Calculation of trust value for COD inventory took 7.152557373046875e-06s
INFO | --- Analysis for cod-inventory took 2.9144277572631836s
Availability | SPARQL endpoint availability check for Cooperation Databank took 0.3099937438964844s
Availability | VoID file availability check for Cooperation Databank took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.2706112861633301s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 4.0531158447265625e-05s
Believability | Calculation of trust value for Cooperation Databank took 8.106231689453125e-06s
INFO | --- Analysis for CoDa took 2.7248013019561768s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.482269287109375e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.2725403308868408s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.020917415618896484s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.314018249511719e-05s
Believability | Calculation of trust value for CODE Endpoint took 7.152557373046875e-06s
INFO | --- Analysis for code-endpoint took 2.9179000854492188s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 0.5546212196350098s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.24106073379516602s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.02134871482849121s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.552436828613281e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 9.775161743164062e-06s
INFO | --- Analysis for coins-openuplabs took 2.9390151500701904s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 3.425551176071167s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.26300668716430664s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02067279815673828s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.511543273925781e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 7.62939453125e-06s
INFO | --- Analysis for CoLChina_sp2000 took 7.189776659011841s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 0.05095267295837402s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.24639582633972168s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 4.00543212890625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for colinda took 2.4153480529785156s
Availability | SPARQL endpoint availability check for CN  2012 took 26.307466506958008s
Availability | VoID file availability check for CN  2012 took 0.0009431838989257812s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.29324865341186523s
Reputation | Calculation of the PageRank for CN  2012 took 0.02194976806640625s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.001134634017944336s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 5.054473876953125e-05s
Believability | Calculation of trust value for CN  2012 took 1.0251998901367188e-05s
INFO | --- Analysis for combined-nomenclature-2012 took 125.38735866546631s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.00543212890625e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.29149460792541504s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.170967102050781e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 9.059906005859375e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 3.4477975368499756s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.1961669921875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.2813146114349365s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.123283386230469e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 6.198883056640625e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 3.3342976570129395s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.3392181396484375e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2491929531097412s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.021708250045776367s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.504753112792969e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 8.821487426757812e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.9592947959899902s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.1961669921875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2736387252807617s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.9802322387695312e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 9.298324584960938e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.907252073287964s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.220008850097656e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.25046777725219727s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.02118539810180664s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.314018249511719e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 7.62939453125e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.952470064163208s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 0.4171788692474365s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0006244182586669922s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.2851369380950928s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02068638801574707s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for CompHistSem took 3.9059929847717285s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 2.103067636489868s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.27201199531555176s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.695487976074219e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 6.9141387939453125e-06s
INFO | --- Analysis for comsode-d3-2 took 7.634497165679932s
Availability | SPARQL endpoint availability check for ConceptNet took 4.172325134277344e-05s
Availability | VoID file availability check for ConceptNet took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.2508554458618164s
Reputation | Calculation of the PageRank for ConceptNet took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.075599670410156e-05s
Believability | Calculation of trust value for ConceptNet took 7.152557373046875e-06s
INFO | --- Analysis for conceptnet took 2.8969712257385254s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.7206878662109375e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0006985664367675781s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2648642063140869s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.487701416015625e-05s
Believability | Calculation of trust value for 2011 US Congress People took 5.245208740234375e-06s
INFO | --- Analysis for congresspeople took 2.9935083389282227s
Availability | SPARQL endpoint availability check for MIMO took 0.28441572189331055s
Availability | VoID file availability check for MIMO took 0.000614166259765625s
Completeness | Calculation of interlinking completeness for MIMO took 0.27916479110717773s
Reputation | Calculation of the PageRank for MIMO took 0.02071070671081543s
Interlinking | Calculation of Degree of Connection for MIMO took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.2874603271484375e-05s
Believability | Calculation of trust value for MIMO took 9.298324584960938e-06s
INFO | --- Analysis for CONNECTED took 3.6394219398498535s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.9114227294921875e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.2533907890319824s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.24249267578125e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 8.58306884765625e-06s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.848112106323242s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.076957702636719e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.2610585689544678s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.02049422264099121s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 2.86102294921875e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 6.67572021484375e-06s
INFO | --- Analysis for copac-library-catalogue took 2.933732748031616s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.363059997558594e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0005435943603515625s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.28132200241088867s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020581722259521484s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.9802322387695312e-05s
Believability | Calculation of trust value for Copyright Free Music took 6.67572021484375e-06s
INFO | --- Analysis for Copyright_Free_Music took 3.573577642440796s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.363059997558594e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.2804713249206543s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.02075362205505371s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0009570121765136719s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 9.894371032714844e-05s
Believability | Calculation of trust value for CopyrightTermBank took 7.62939453125e-06s
INFO | --- Analysis for copyrighttermbank took 36.52494764328003s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 1.9625396728515625s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0007870197296142578s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.3319664001464844s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.023058652877807617s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 4.0531158447265625e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 7.152557373046875e-06s
INFO | --- Analysis for core took 7.056657791137695s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 0.585695743560791s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.000263214111328125s
Extra | Recovery of all triples for Corine linked dataset @PSNC took 96.97193956375122s
Performance | Total latancy measurement for Corine linked dataset @PSNC took 1.0538690090179443s
Amount of data | Number of triples check for Corine linked dataset @PSNC took 8.081024169921875s
Interoperability | New terms check for Corine linked dataset @PSNC took 15.427764177322388s
Versatility | Languages check for Corine linked dataset @PSNC took 300.2472538948059s
Interpretability | Number of blank nodes check for Corine linked dataset @PSNC took 3.170919179916382s
Interpretability | RDF structures check for Corine linked dataset @PSNC took 0.2838718891143799s
Versatility | Serialization formats check for Corine linked dataset @PSNC took 9.06400752067566s
Availability | RDF dump link check for Corine linked dataset @PSNC took 0.2653050422668457s
License | MR license check for Corine linked dataset @PSNC took 0.5744154453277588s
License | HR license check for Corine linked dataset @PSNC took 300.2011981010437s
Amount of data | Number of property check for Corine linked dataset @PSNC took 0.31443238258361816s
Understandability | Number of label check for Corine linked dataset @PSNC took 2.807197332382202s
Understandability | URI regex check for Corine linked dataset @PSNC took 0.8088257312774658s
Understandability | Vocabs check for Corine linked dataset @PSNC took 0.44841670989990234s
Verifiability | Authors check for Corine linked dataset @PSNC took 0.18179869651794434s
Verifiability | Publishers check for Corine linked dataset @PSNC took 0.255983829498291s
Performance | Throughput check for Corine linked dataset @PSNC took 11.320870399475098s
Amount of data | Check the number of entities for Corine linked dataset @PSNC took 7.963180541992188e-05s
Verifiability | Contribs. check for Corine linked dataset @PSNC took 0.21657609939575195s
Interlinking | sameAs chians check for Corine linked dataset @PSNC took 0.19560956954956055s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4478487968444824s
Interlinking | skos check for Corine linked dataset @PSNC took 0.4286966323852539s
Timeliness | dataset update frequency check for Corine linked dataset @PSNC took 5.537364721298218s
Currency | Creation date check for Corine linked dataset @PSNC took 0.5006446838378906s
Currency | Modification date check for Corine linked dataset @PSNC took 0.23490524291992188s
Rep.Conc. | URIs length for Corine linked dataset @PSNC took 151.21991300582886s
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.18535304069519043s
Accuracy | Check Functional Property for Corine linked dataset @PSNC took 0.290010929107666s
Accuracy | Check Inverse Functional Property for Corine linked dataset @PSNC took 0.3173859119415283s
Accuracy | Check Empty annotation labels for Corine linked dataset @PSNC took 39.455387592315674s
Accuracy | Check White space in annotation for Corine linked dataset @PSNC took 2.683351755142212s
Accuracy | Check Datatype consistency for Corine linked dataset @PSNC took 2.5970499515533447s
Consistency | Disjoint class check for Corine linked dataset @PSNC took 0.18929243087768555s
Consistency | Check Misplaced properties for Corine linked dataset @PSNC took 82.73054933547974s
Consistency | Misplaced classes for Corine linked dataset @PSNC took 8.319576978683472s
Consistency | Check Ontology hijacking for Corine linked dataset @PSNC took 29.337915420532227s
Consistency | Check Invalid usage of undefined classes for Corine linked dataset @PSNC took 1.4421889781951904s
Consistency | Check Invalid usage of undefined properties for Corine linked dataset @PSNC took 84.71453905105591s
Conciseness | Check Extensional conciseness for Corine linked dataset @PSNC took 2.7971482276916504s
Conciseness | Check Intensional conciseness for Corine linked dataset @PSNC took 0.519655704498291s
Security | Sign check for Corine linked dataset @PSNC took 0.7103803157806396s
Availability | Check URIs Dereferenciability for Corine linked dataset @PSNC took 9.613033056259155s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 1.6311819553375244s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for Corine linked dataset @PSNC took 1.430511474609375e-06s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for Corine_linked_dataset took 2227.834138393402s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.601478576660156e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.27001166343688965s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020908117294311523s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.933906555175781e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.106231689453125e-06s
INFO | --- Analysis for corn took 4.701660633087158s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00014281272888183594s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.689873456954956s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 2.86102294921875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 6.9141387939453125e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 3.748663902282715s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 7.295608520507812e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.2831382751464844s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.9325485229492188e-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 3.3910319805145264s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.315376281738281e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0006163120269775391s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.27124762535095215s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.793571472167969e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.2159347534179688e-05s
INFO | --- Analysis for cornetto took 13.45719051361084s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 0.17521214485168457s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.0005731582641601562s
Extra | Recovery of all triples for Corporate Body Named Authority List  took 78.36237692832947s
Performance | Total latancy measurement for Corporate Body Named Authority List  took 0.630535364151001s
Amount of data | Number of triples check for Corporate Body Named Authority List  took 0.5804996490478516s
Interoperability | New terms check for Corporate Body Named Authority List  took 11.877222776412964s
Versatility | Languages check for Corporate Body Named Authority List  took 300.06519651412964s
Interpretability | Number of blank nodes check for Corporate Body Named Authority List  took 1.9609723091125488s
Security | Check HTTPS for Corporate Body Named Authority List  took 0.3529398441314697s
Interpretability | RDF structures check for Corporate Body Named Authority List  took 0.3929741382598877s
Versatility | Serialization formats check for Corporate Body Named Authority List  took 2.31378436088562s
Availability | RDF dump link check for Corporate Body Named Authority List  took 0.3170456886291504s
License | MR license check for Corporate Body Named Authority List  took 0.15526366233825684s
License | HR license check for Corporate Body Named Authority List  took 300.0145905017853s
Amount of data | Number of property check for Corporate Body Named Authority List  took 0.17400169372558594s
Understandability | Number of label check for Corporate Body Named Authority List  took 1.1284351348876953s
Understandability | URI regex check for Corporate Body Named Authority List  took 0.264575719833374s
Understandability | Vocabs check for Corporate Body Named Authority List  took 0.0908348560333252s
Verifiability | Authors check for Corporate Body Named Authority List  took 0.1475687026977539s
Verifiability | Publishers check for Corporate Body Named Authority List  took 0.1480569839477539s
Performance | Throughput check for Corporate Body Named Authority List  took 10.620544910430908s
Amount of data | Check the number of entities for Corporate Body Named Authority List  took 0.00010848045349121094s
Verifiability | Contribs. check for Corporate Body Named Authority List  took 0.13939905166625977s
Interlinking | sameAs chians check for Corporate Body Named Authority List  took 0.9382846355438232s
Interlinking | skos check for Corporate Body Named Authority List  took 0.3762035369873047s
Interlinking | skos check for Corporate Body Named Authority List  took 0.35656261444091797s
Timeliness | dataset update frequency check for Corporate Body Named Authority List  took 0.17338132858276367s
Currency | Creation date check for Corporate Body Named Authority List  took 0.26227355003356934s
Currency | Modification date check for Corporate Body Named Authority List  took 0.25844597816467285s
Rep.Conc. | URIs length for Corporate Body Named Authority List  took 97.39105701446533s
Interoperability | New vocabularies check for Corporate Body Named Authority List  took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Corporate Body Named Authority List  took 0.19281244277954102s
Accuracy | Check Functional Property for Corporate Body Named Authority List  took 0.17439985275268555s
Accuracy | Check Inverse Functional Property for Corporate Body Named Authority List  took 0.17141151428222656s
Accuracy | Check Empty annotation labels for Corporate Body Named Authority List  took 21.50169086456299s
Accuracy | Check White space in annotation for Corporate Body Named Authority List  took 3.1195359230041504s
Accuracy | Check Datatype consistency for Corporate Body Named Authority List  took 2.6837267875671387s
Consistency | Disjoint class check for Corporate Body Named Authority List  took 0.10946178436279297s
Consistency | Check Misplaced properties for Corporate Body Named Authority List  took 55.24274182319641s
Consistency | Misplaced classes for Corporate Body Named Authority List  took 8.585585355758667s
Consistency | Check Ontology hijacking for Corporate Body Named Authority List  took 25.259538650512695s
Consistency | Check Invalid usage of undefined classes for Corporate Body Named Authority List  took 1.5506103038787842s
Consistency | Check Invalid usage of undefined properties for Corporate Body Named Authority List  took 57.08252787590027s
Conciseness | Check Extensional conciseness for Corporate Body Named Authority List  took 2.960972547531128s
Conciseness | Check Intensional conciseness for Corporate Body Named Authority List  took 0.39796900749206543s
Security | Sign check for Corporate Body Named Authority List  took 0.10437870025634766s
Availability | Check URIs Dereferenciability for Corporate Body Named Authority List  took 8.699049711227417s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 1.2571375370025635s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.021140098571777344s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007796287536621094s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Corporate Body Named Authority List  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 6.9141387939453125e-06s
INFO | --- Analysis for corporate-body took 13421.828724861145s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 0.6075000762939453s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.7058124542236328s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.02140665054321289s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 4.482269287109375e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for CorpusFibonacci took 5.298970460891724s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.100799560546875e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.6911778450012207s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.021396875381469727s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007846355438232422s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 3.600120544433594e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.0251998901367188e-05s
INFO | --- Analysis for corscheck took 3.870981454849243s
Availability | SPARQL endpoint availability check for Country Name Authority List took 0.1818523406982422s
Availability | VoID file availability check for Country Name Authority List took 0.0007259845733642578s
Extra | Recovery of all triples for Country Name Authority List took 66.25528383255005s
Performance | Total latancy measurement for Country Name Authority List took 0.5997400283813477s
Amount of data | Number of triples check for Country Name Authority List took 0.8770039081573486s
Interoperability | New terms check for Country Name Authority List took 12.581171751022339s
Versatility | Languages check for Country Name Authority List took 300.0859944820404s
Interpretability | Number of blank nodes check for Country Name Authority List took 1.9995753765106201s
Security | Check HTTPS for Country Name Authority List took 0.3323211669921875s
Interpretability | RDF structures check for Country Name Authority List took 0.4170365333557129s
Versatility | Serialization formats check for Country Name Authority List took 2.3011863231658936s
Availability | RDF dump link check for Country Name Authority List took 0.2176952362060547s
License | MR license check for Country Name Authority List took 0.248748779296875s
License | HR license check for Country Name Authority List took 300.0815739631653s
Amount of data | Number of property check for Country Name Authority List took 0.1783764362335205s
Understandability | Number of label check for Country Name Authority List took 0.8564341068267822s
Understandability | URI regex check for Country Name Authority List took 0.2457582950592041s
Understandability | Vocabs check for Country Name Authority List took 0.10270833969116211s
Verifiability | Authors check for Country Name Authority List took 0.11191463470458984s
Verifiability | Publishers check for Country Name Authority List took 0.2686934471130371s
Performance | Throughput check for Country Name Authority List took 10.685861349105835s
Amount of data | Check the number of entities for Country Name Authority List took 7.414817810058594e-05s
Verifiability | Contribs. check for Country Name Authority List took 0.08804965019226074s
Interlinking | sameAs chians check for Country Name Authority List took 0.7852916717529297s
Interlinking | skos check for Country Name Authority List took 0.35384297370910645s
Interlinking | skos check for Country Name Authority List took 0.1633133888244629s
Timeliness | dataset update frequency check for Country Name Authority List took 0.24500751495361328s
Currency | Creation date check for Country Name Authority List took 0.3145885467529297s
Currency | Modification date check for Country Name Authority List took 0.1989302635192871s
Rep.Conc. | URIs length for Country Name Authority List took 104.29821109771729s
Interoperability | New vocabularies check for Country Name Authority List took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Country Name Authority List took 0.13572955131530762s
Accuracy | Check Functional Property for Country Name Authority List took 0.23270726203918457s
Accuracy | Check Inverse Functional Property for Country Name Authority List took 0.15668320655822754s
Accuracy | Check Empty annotation labels for Country Name Authority List took 38.27108550071716s
Accuracy | Check White space in annotation for Country Name Authority List took 3.113616466522217s
Accuracy | Check Datatype consistency for Country Name Authority List took 2.6474664211273193s
Consistency | Disjoint class check for Country Name Authority List took 0.1804184913635254s
Consistency | Check Misplaced properties for Country Name Authority List took 53.39558005332947s
Consistency | Misplaced classes for Country Name Authority List took 8.313491106033325s
Consistency | Check Ontology hijacking for Country Name Authority List took 35.574005365371704s
Consistency | Check Invalid usage of undefined classes for Country Name Authority List took 1.4510977268218994s
Consistency | Check Invalid usage of undefined properties for Country Name Authority List took 54.389235973358154s
Conciseness | Check Extensional conciseness for Country Name Authority List took 3.012367010116577s
Conciseness | Check Intensional conciseness for Country Name Authority List took 0.4053053855895996s
Security | Sign check for Country Name Authority List took 0.1098794937133789s
Availability | Check URIs Dereferenciability for Country Name Authority List took 8.807445287704468s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 1.152686595916748s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.021920442581176758s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 5.841255187988281e-05s
Interoperability | Check the re-using of existing vocabs for Country Name Authority List took 1.6689300537109375e-06s
Believability | Calculation of trust value for Country Name Authority List took 6.4373016357421875e-06s
INFO | --- Analysis for country-authority-list took 14177.847031593323s
Availability | SPARQL endpoint availability check for Courts thesaurus took 0.07942032814025879s
Availability | VoID file availability check for Courts thesaurus took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2769441604614258s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.890296936035156e-05s
Believability | Calculation of trust value for Courts thesaurus took 2.8848648071289062e-05s
INFO | --- Analysis for courts-thesaurus took 4.888726472854614s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 0.7821180820465088s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2865335941314697s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.021275043487548828s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 8.344650268554688e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 7.867813110351562e-06s
INFO | --- Analysis for Covid-on-the-Web took 6.427021503448486s
Availability | SPARQL endpoint availability check for CPA 2008 took 26.027443647384644s
Availability | VoID file availability check for CPA 2008 took 0.0008234977722167969s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2870826721191406s
Reputation | Calculation of the PageRank for CPA 2008 took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.00543212890625e-05s
Believability | Calculation of trust value for CPA 2008 took 5.4836273193359375e-06s
INFO | --- Analysis for cpa-2008 took 127.88329339027405s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 0.34247255325317383s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0013124942779541016s
Extra | Recovery of all triples for Cooperative Patent Classification took 53.18681740760803s
Performance | Total latancy measurement for Cooperative Patent Classification took 0.9206202030181885s
Amount of data | Number of triples check for Cooperative Patent Classification took 90.13748455047607s
Versatility | Languages check for Cooperative Patent Classification took 120.10464239120483s
Interpretability | Number of blank nodes check for Cooperative Patent Classification took 90.21850633621216s
Interpretability | RDF structures check for Cooperative Patent Classification took 0.2092573642730713s
Versatility | Serialization formats check for Cooperative Patent Classification took 0.2038280963897705s
Availability | RDF dump link check for Cooperative Patent Classification took 0.17337727546691895s
License | MR license check for Cooperative Patent Classification took 0.1678781509399414s
License | HR license check for Cooperative Patent Classification took 90.21330118179321s
Amount of data | Number of property check for Cooperative Patent Classification took 0.26044607162475586s
Understandability | Number of label check for Cooperative Patent Classification took 90.1661696434021s
Understandability | URI regex check for Cooperative Patent Classification took 0.5591027736663818s
Understandability | Vocabs check for Cooperative Patent Classification took 0.1779482364654541s
Verifiability | Authors check for Cooperative Patent Classification took 0.180619478225708s
Verifiability | Publishers check for Cooperative Patent Classification took 0.16023612022399902s
Performance | Throughput check for Cooperative Patent Classification took 10.69813847541809s
Amount of data | Check the number of entities for Cooperative Patent Classification took 7.343292236328125e-05s
Verifiability | Contribs. check for Cooperative Patent Classification took 0.16844725608825684s
Interlinking | sameAs chians check for Cooperative Patent Classification took 0.13193464279174805s
Interlinking | skos check for Cooperative Patent Classification took 0.2565457820892334s
Interlinking | skos check for Cooperative Patent Classification took 0.1874222755432129s
Timeliness | dataset update frequency check for Cooperative Patent Classification took 0.17557454109191895s
Currency | Creation date check for Cooperative Patent Classification took 0.3725087642669678s
Currency | Modification date check for Cooperative Patent Classification took 0.36263251304626465s
Rep.Conc. | URIs length for Cooperative Patent Classification took 156.84716033935547s
Interoperability | New vocabularies check for Cooperative Patent Classification took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for Cooperative Patent Classification took 0.1600356101989746s
Accuracy | Check Empty annotation labels for Cooperative Patent Classification took 18.067583799362183s
Accuracy | Check White space in annotation for Cooperative Patent Classification took 2.9757583141326904s
Accuracy | Check Datatype consistency for Cooperative Patent Classification took 4.901586294174194s
Consistency | Disjoint class check for Cooperative Patent Classification took 0.18324542045593262s
Consistency | Check Misplaced properties for Cooperative Patent Classification took 120.35275793075562s
Consistency | Check Ontology hijacking for Cooperative Patent Classification took 22.625291347503662s
Consistency | Check Invalid usage of undefined classes for Cooperative Patent Classification took 1.619875192642212s
Consistency | Check Invalid usage of undefined properties for Cooperative Patent Classification took 121.43141674995422s
Conciseness | Check Extensional conciseness for Cooperative Patent Classification took 2.808161735534668s
Conciseness | Check Intensional conciseness for Cooperative Patent Classification took 0.2787034511566162s
Security | Sign check for Cooperative Patent Classification took 0.16118335723876953s
Availability | Check URIs Dereferenciability for Cooperative Patent Classification took 1.3025250434875488s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.5172402858734131s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 4.6253204345703125e-05s
Interoperability | Check the re-using of existing vocabs for Cooperative Patent Classification took 1.6689300537109375e-06s
Believability | Calculation of trust value for Cooperative Patent Classification took 7.62939453125e-06s
INFO | --- Analysis for CPC took 1321.7734746932983s
Availability | SPARQL endpoint availability check for CPC 2008 took 26.48251986503601s
Availability | VoID file availability check for CPC 2008 took 0.0010209083557128906s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.28124070167541504s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.743171691894531e-05s
Believability | Calculation of trust value for CPC 2008 took 7.62939453125e-06s
INFO | --- Analysis for cpc-2008 took 127.96881866455078s
Availability | SPARQL endpoint availability check for CPV  2003 took 20.491540670394897s
Availability | VoID file availability check for CPV  2003 took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.3631737232208252s
Reputation | Calculation of the PageRank for CPV  2003 took 0.020786046981811523s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 4.172325134277344e-05s
Believability | Calculation of trust value for CPV  2003 took 5.9604644775390625e-06s
INFO | --- Analysis for cpv-2003 took 116.14528703689575s
Availability | SPARQL endpoint availability check for CPV 2008 took 24.385209321975708s
Availability | VoID file availability check for CPV 2008 took 0.0009140968322753906s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.7161922454833984s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 5.221366882324219e-05s
Believability | Calculation of trust value for CPV 2008 took 5.4836273193359375e-06s
INFO | --- Analysis for cpv-2008 took 126.54988098144531s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 260.3956413269043s
Availability | VoID file availability check for crowdsourcing-fb took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.37281012535095215s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.020821094512939453s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 4.172325134277344e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.198883056640625e-06s
INFO | --- Analysis for crowdsourcing-fb took 535.4004471302032s
Availability | SPARQL endpoint availability check for CRTM took 4.124641418457031e-05s
Availability | VoID file availability check for CRTM took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for CRTM took 0.26756739616394043s
Reputation | Calculation of the PageRank for CRTM took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for CRTM took 3.361701965332031e-05s
Believability | Calculation of trust value for CRTM took 8.106231689453125e-06s
INFO | --- Analysis for crtm took 4.74767279624939s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 8.96453857421875e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.25599098205566406s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 2.8848648071289062e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 6.198883056640625e-06s
INFO | --- Analysis for crystal-eye took 3.3946797847747803s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 6.883747577667236s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.34674644470214844s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.021042823791503906s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0010311603546142578s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 5.841255187988281e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 5.4836273193359375e-06s
INFO | --- Analysis for ctic-public-dataset took 45.004228591918945s
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.00026607513427734375s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.2607104778289795s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.0040740966796875e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.867813110351562e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.9509963989257812s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.49741196632385254s
Availability | VoID file availability check for CulturaLinkedData took 0.0005085468292236328s
Extra | Recovery of all triples for CulturaLinkedData took 143.83621072769165s
Performance | Total latancy measurement for CulturaLinkedData took 6.191013336181641s
Amount of data | Number of triples check for CulturaLinkedData took 3.169982433319092s
Interoperability | New terms check for CulturaLinkedData took 2.401695966720581s
Versatility | Languages check for CulturaLinkedData took 62.77087736129761s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.19627714157104492s
Interpretability | RDF structures check for CulturaLinkedData took 0.3659546375274658s
Versatility | Serialization formats check for CulturaLinkedData took 2.100254535675049s
Availability | RDF dump link check for CulturaLinkedData took 0.22746849060058594s
License | MR license check for CulturaLinkedData took 2.3658511638641357s
License | HR license check for CulturaLinkedData took 62.048810720443726s
Amount of data | Number of property check for CulturaLinkedData took 2.0313591957092285s
Understandability | Number of label check for CulturaLinkedData took 2.547030210494995s
Understandability | URI regex check for CulturaLinkedData took 2.2944657802581787s
Understandability | Vocabs check for CulturaLinkedData took 2.0862526893615723s
Verifiability | Authors check for CulturaLinkedData took 2.119554281234741s
Verifiability | Publishers check for CulturaLinkedData took 2.0520119667053223s
Performance | Throughput check for CulturaLinkedData took 21.853875160217285s
Amount of data | Check the number of entities for CulturaLinkedData took 0.00010967254638671875s
Verifiability | Contribs. check for CulturaLinkedData took 2.0286970138549805s
Interlinking | sameAs chians check for CulturaLinkedData took 2.171478271484375s
Interlinking | skos check for CulturaLinkedData took 0.4014251232147217s
Interlinking | skos check for CulturaLinkedData took 2.0130116939544678s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.30377697944641113s
Currency | Creation date check for CulturaLinkedData took 4.07747220993042s
Currency | Modification date check for CulturaLinkedData took 2.0929744243621826s
Rep.Conc. | URIs length for CulturaLinkedData took 70.81579184532166s
Interoperability | New vocabularies check for CulturaLinkedData took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 1.8710472583770752s
Accuracy | Check Functional Property for CulturaLinkedData took 2.004648447036743s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.1912248134613037s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 42.00648808479309s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.5954031944274902s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.321028709411621s
Consistency | Disjoint class check for CulturaLinkedData took 0.2410907745361328s
Consistency | Check Misplaced properties for CulturaLinkedData took 7.998613357543945s
Consistency | Misplaced classes for CulturaLinkedData took 5.95949912071228s
Consistency | Check Ontology hijacking for CulturaLinkedData took 40.70159935951233s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3784394264221191s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 10.986028909683228s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3778293132781982s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.2001025676727295s
Security | Sign check for CulturaLinkedData took 2.7181084156036377s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 11.253635883331299s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.7567605972290039s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.02118206024169922s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.9073486328125e-06s
Believability | Calculation of trust value for CulturaLinkedData took 7.3909759521484375e-06s
INFO | --- Analysis for culturalinkeddata took 680.160781621933s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.45845842361450195s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0007410049438476562s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.7158722877502441s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.02047586441040039s
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.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-ares-or took 4.917548656463623s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.10997939109802246s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.27754640579223633s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02060389518737793s
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.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.552436828613281e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.245208740234375e-06s
INFO | --- Analysis for cz-ares-rzp took 2.837414503097534s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 0.11291146278381348s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.44275927543640137s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.021085500717163086s
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.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.528594970703125e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 4.76837158203125e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 3.5283830165863037s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 0.11233353614807129s
Availability | VoID file availability check for Integrated pollution registry took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.7062139511108398s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0008864402770996094s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.7670135498046875e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.7404556274414062e-05s
INFO | --- Analysis for cz-cenia-pollution took 3.7505061626434326s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 0.10893535614013672s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.27086663246154785s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.504753112792969e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 5.245208740234375e-06s
INFO | --- Analysis for cz-contracts took 3.2078850269317627s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 7.200241088867188e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.27201366424560547s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.8848648071289062e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-courts took 3.8475677967071533s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 0.10857439041137695s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.28179383277893066s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02015542984008789s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 4.76837158203125e-06s
INFO | --- Analysis for cz-ctia-bans took 5.540207386016846s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 0.1045694351196289s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0007719993591308594s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.261915922164917s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020510435104370117s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.5762786865234375e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 7.867813110351562e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.7826054096221924s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.11008167266845703s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.297396183013916s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020574092864990234s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.5762786865234375e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-focus took 2.7867579460144043s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 0.10963940620422363s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2832059860229492s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.887580871582031e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 5.7220458984375e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.818918228149414s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 0.12038207054138184s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.0005652904510498047s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.24834084510803223s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.6716461181640625e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 5.245208740234375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 4.9133734703063965s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 0.21204447746276855s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.2767152786254883s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.022094011306762695s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0009779930114746094s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.649162292480469e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 5.0067901611328125e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 3.2842960357666016s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.11160898208618164s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.24359869956970215s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.266334533691406e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 4.76837158203125e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.8413379192352295s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 0.8102316856384277s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.0005481243133544922s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.2674379348754883s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-average-salaries took 3.846331834793091s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 0.40225839614868164s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.26610255241394043s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.8623809814453125e-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.3561065196990967s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.4723975658416748s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.29299449920654297s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.695487976074219e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 3.3395941257476807s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 0.42033982276916504s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2925431728363037s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.020600318908691406s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-job-applicants took 3.3295814990997314s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.46762561798095703s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2844204902648926s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 3.421862840652466s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.383681058883667s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2803525924682617s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007307529449462891s
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 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-regions took 3.064507246017456s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 0.3818988800048828s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.27091479301452637s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 3.374140501022339s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 0.42209339141845703s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.2634575366973877s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.647804260253906e-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.3659517765045166s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 0.38772034645080566s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2584359645843506s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.022731781005859375s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0008029937744140625s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 4.291534423828125e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.0067901611328125e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 3.294456958770752s
Availability | SPARQL endpoint availability check for ATC groups took 0.1121211051940918s
Availability | VoID file availability check for ATC groups took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2762644290924072s
Reputation | Calculation of the PageRank for ATC groups took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ATC groups took 7.748603820800781e-05s
Believability | Calculation of trust value for ATC groups took 6.198883056640625e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.691030740737915s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.11280202865600586s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.25856614112854004s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020622968673706055s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.4809112548828125e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 5.7220458984375e-06s
INFO | --- Analysis for cz-fulfillments took 2.8466897010803223s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 0.04510164260864258s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005750656127929688s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.28711915016174316s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020122289657592773s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.7206878662109375e-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.1483633518218994s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 0.12626957893371582s
Availability | VoID file availability check for List of Czech data boxes took 0.0005397796630859375s
Extra | Recovery of all triples for List of Czech data boxes took 301.16740560531616s
Performance | Total latancy measurement for List of Czech data boxes took 0.6215267181396484s
Amount of data | Number of triples check for List of Czech data boxes took 75.81644010543823s
Interoperability | New terms check for List of Czech data boxes took 20.79054045677185s
Versatility | Languages check for List of Czech data boxes took 300.156592130661s
Interpretability | Number of blank nodes check for List of Czech data boxes took 2.7606074810028076s
Interpretability | RDF structures check for List of Czech data boxes took 0.2609739303588867s
Versatility | Serialization formats check for List of Czech data boxes took 0.5635595321655273s
Availability | RDF dump link check for List of Czech data boxes took 14.588876962661743s
License | MR license check for List of Czech data boxes took 0.5217821598052979s
License | HR license check for List of Czech data boxes took 275.02366495132446s
Amount of data | Number of property check for List of Czech data boxes took 0.141923189163208s
Understandability | Number of label check for List of Czech data boxes took 3.6332767009735107s
Understandability | URI regex check for List of Czech data boxes took 0.5422015190124512s
Understandability | Vocabs check for List of Czech data boxes took 0.2724461555480957s
Verifiability | Authors check for List of Czech data boxes took 0.48566532135009766s
Verifiability | Publishers check for List of Czech data boxes took 0.14633393287658691s
Performance | Throughput check for List of Czech data boxes took 10.426164388656616s
Amount of data | Check the number of entities for List of Czech data boxes took 3.054075002670288s
Verifiability | Contribs. check for List of Czech data boxes took 0.5997629165649414s
Interlinking | sameAs chians check for List of Czech data boxes took 1.2413158416748047s
Interlinking | skos check for List of Czech data boxes took 0.2574315071105957s
Interlinking | skos check for List of Czech data boxes took 0.11025023460388184s
Timeliness | dataset update frequency check for List of Czech data boxes took 0.35306620597839355s
Currency | Creation date check for List of Czech data boxes took 1.8982229232788086s
Currency | Modification date check for List of Czech data boxes took 0.4346952438354492s
Rep.Conc. | URIs length for List of Czech data boxes took 267.2992377281189s
Interoperability | New vocabularies check for List of Czech data boxes took 54.10815954208374s
Consistency | Deprecated classes/propertiers check for List of Czech data boxes took 0.45061492919921875s
Accuracy | Check Functional Property for List of Czech data boxes took 0.15415620803833008s
Accuracy | Check Inverse Functional Property for List of Czech data boxes took 0.16684794425964355s
Accuracy | Check Empty annotation labels for List of Czech data boxes took 96.49902129173279s
Accuracy | Check White space in annotation for List of Czech data boxes took 3.064751625061035s
Accuracy | Check Datatype consistency for List of Czech data boxes took 2.6158854961395264s
Consistency | Disjoint class check for List of Czech data boxes took 0.2542123794555664s
Consistency | Check Misplaced properties for List of Czech data boxes took 147.7868366241455s
Consistency | Misplaced classes for List of Czech data boxes took 8.036490678787231s
Consistency | Check Ontology hijacking for List of Czech data boxes took 81.04581427574158s
Consistency | Check Invalid usage of undefined classes for List of Czech data boxes took 1.437072515487671s
Consistency | Check Invalid usage of undefined properties for List of Czech data boxes took 124.46877217292786s
Conciseness | Check Extensional conciseness for List of Czech data boxes took 2.6642208099365234s
Conciseness | Check Intensional conciseness for List of Czech data boxes took 1.0815799236297607s
Security | Sign check for List of Czech data boxes took 0.14193081855773926s
Availability | Check URIs Dereferenciability for List of Czech data boxes took 12.208740949630737s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.8233368396759033s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020902633666992188s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.981590270996094e-05s
Interoperability | Check the re-using of existing vocabs for List of Czech data boxes took 57.621634006500244s
Believability | Calculation of trust value for List of Czech data boxes took 6.4373016357421875e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2599.076915502548s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12472128868103027s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0006480216979980469s
Extra | Recovery of all triples for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 292.50842118263245s
Performance | Total latancy measurement for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.6139857769012451s
Amount of data | Number of triples check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 18.174007415771484s
Interoperability | New terms check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 21.13720965385437s
Versatility | Languages check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 300.154016494751s
Interpretability | Number of blank nodes check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.329097032546997s
Interpretability | RDF structures check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1280961036682129s
Versatility | Serialization formats check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.9320971965789795s
Availability | RDF dump link check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 16.618871688842773s
License | MR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11386919021606445s
License | HR license check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 231.733336687088s
Amount of data | Number of property check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11574316024780273s
Understandability | Number of label check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 6.60920786857605s
Understandability | URI regex check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.2604827880859375s
Understandability | Vocabs check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11397147178649902s
Verifiability | Authors check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.37639451026916504s
Verifiability | Publishers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17159342765808105s
Performance | Throughput check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 10.481905221939087s
Amount of data | Check the number of entities for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.0678744316101074s
Verifiability | Contribs. check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7269206047058105s
Interlinking | sameAs chians check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.38306689262390137s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11258864402770996s
Interlinking | skos check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.10875129699707031s
Timeliness | dataset update frequency check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17973899841308594s
Currency | Creation date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.7403388023376465s
Currency | Modification date check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.204850435256958s
Rep.Conc. | URIs length for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 258.01280069351196s
Interoperability | New vocabularies check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 101.02716326713562s
Consistency | Deprecated classes/propertiers check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.48986363410949707s
Accuracy | Check Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.12362170219421387s
Accuracy | Check Inverse Functional Property for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.1227719783782959s
Accuracy | Check Empty annotation labels for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 101.65499114990234s
Accuracy | Check White space in annotation for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.117780923843384s
Accuracy | Check Datatype consistency for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.6346795558929443s
Consistency | Disjoint class check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.13996148109436035s
Consistency | Check Misplaced properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 135.47128796577454s
Consistency | Misplaced classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.820399045944214s
Consistency | Check Ontology hijacking for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 81.78928351402283s
Consistency | Check Invalid usage of undefined classes for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4979369640350342s
Consistency | Check Invalid usage of undefined properties for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 125.87074089050293s
Conciseness | Check Extensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.743472099304199s
Conciseness | Check Intensional conciseness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.054919958114624s
Security | Sign check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.11223840713500977s
Availability | Check URIs Dereferenciability for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 11.524083852767944s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.4705243110656738s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02068042755126953s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 4.5299530029296875e-05s
Interoperability | Check the re-using of existing vocabs for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 92.72293901443481s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.344650268554688e-06s
INFO | --- Analysis for cz-nace took 2579.1773705482483s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.30787062644958496s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0006055831909179688s
Extra | Recovery of all triples for Czech National Open Data Catalog in DCAT-AP v1.2 took 161.79337000846863s
Performance | Total latancy measurement for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.7959866523742676s
Amount of data | Number of triples check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2463831901550293s
Interoperability | New terms check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.5064735412597656s
Versatility | Languages check for Czech National Open Data Catalog in DCAT-AP v1.2 took 26.7538104057312s
Interpretability | Number of blank nodes check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5324480533599854s
Interpretability | RDF structures check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.26366138458251953s
Versatility | Serialization formats check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.323173999786377s
Availability | RDF dump link check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5533783435821533s
License | MR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.37783360481262207s
License | HR license check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5865590572357178s
Amount of data | Number of property check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1704695224761963s
Understandability | Number of label check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.5136640071868896s
Understandability | URI regex check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.3392658233642578s
Understandability | Vocabs check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.18550348281860352s
Verifiability | Authors check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.23373794555664062s
Verifiability | Publishers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.302898645401001s
Performance | Throughput check for Czech National Open Data Catalog in DCAT-AP v1.2 took 10.59956431388855s
Amount of data | Check the number of entities for Czech National Open Data Catalog in DCAT-AP v1.2 took 7.963180541992188e-05s
Verifiability | Contribs. check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17012476921081543s
Interlinking | sameAs chians check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.20276713371276855s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2978854179382324s
Interlinking | skos check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.1615159511566162s
Timeliness | dataset update frequency check for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.4899158477783203s
Currency | Creation date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.42591166496276855s
Currency | Modification date check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.34852170944213867s
Rep.Conc. | URIs length for Czech National Open Data Catalog in DCAT-AP v1.2 took 55.82870316505432s
Interoperability | New vocabularies check for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.14744067192077637s
Accuracy | Check Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16974854469299316s
Accuracy | Check Inverse Functional Property for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.16271758079528809s
Accuracy | Check Empty annotation labels for Czech National Open Data Catalog in DCAT-AP v1.2 took 42.15875768661499s
Accuracy | Check White space in annotation for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.441335678100586s
Accuracy | Check Datatype consistency for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.7014026641845703s
Consistency | Disjoint class check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17280864715576172s
Consistency | Check Misplaced properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.8747344017028809s
Consistency | Misplaced classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 8.524091958999634s
Consistency | Check Ontology hijacking for Czech National Open Data Catalog in DCAT-AP v1.2 took 88.8558030128479s
Consistency | Check Invalid usage of undefined classes for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.7013013362884521s
Consistency | Check Invalid usage of undefined properties for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.099483013153076s
Conciseness | Check Extensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.1740410327911377s
Conciseness | Check Intensional conciseness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.32512450218200684s
Security | Sign check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.2865605354309082s
Availability | Check URIs Dereferenciability for Czech National Open Data Catalog in DCAT-AP v1.2 took 1046.9490468502045s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.680741548538208s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.021227598190307617s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.3365020751953125e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.57763671875e-05s
Interoperability | Check the re-using of existing vocabs for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.384185791015625e-06s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 5.9604644775390625e-06s
INFO | --- Analysis for cz-nkod took 35454.58980035782s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 0.20899415016174316s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.2817990779876709s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0010263919830322266s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 4.744529724121094e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 9.5367431640625e-06s
INFO | --- Analysis for cz-orders took 3.7627832889556885s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 0.20338749885559082s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0006744861602783203s
Extra | Recovery of all triples for Institutions of public power of the Czech Republic took 304.7658553123474s
Performance | Total latancy measurement for Institutions of public power of the Czech Republic took 0.5692689418792725s
Amount of data | Number of triples check for Institutions of public power of the Czech Republic took 44.141072034835815s
Interoperability | New terms check for Institutions of public power of the Czech Republic took 20.917029857635498s
Versatility | Languages check for Institutions of public power of the Czech Republic took 300.1678194999695s
Interpretability | Number of blank nodes check for Institutions of public power of the Czech Republic took 7.903555154800415s
Interpretability | RDF structures check for Institutions of public power of the Czech Republic took 0.3719766139984131s
Versatility | Serialization formats check for Institutions of public power of the Czech Republic took 5.532564163208008s
Availability | RDF dump link check for Institutions of public power of the Czech Republic took 14.647353887557983s
License | MR license check for Institutions of public power of the Czech Republic took 0.13441801071166992s
License | HR license check for Institutions of public power of the Czech Republic took 300.10629630088806s
Amount of data | Number of property check for Institutions of public power of the Czech Republic took 0.2755894660949707s
Understandability | Number of label check for Institutions of public power of the Czech Republic took 10.18056583404541s
Understandability | URI regex check for Institutions of public power of the Czech Republic took 0.3384439945220947s
Understandability | Vocabs check for Institutions of public power of the Czech Republic took 0.2463846206665039s
Verifiability | Authors check for Institutions of public power of the Czech Republic took 0.746734619140625s
Verifiability | Publishers check for Institutions of public power of the Czech Republic took 0.13938260078430176s
Performance | Throughput check for Institutions of public power of the Czech Republic took 10.611868143081665s
Amount of data | Check the number of entities for Institutions of public power of the Czech Republic took 3.139655351638794s
Verifiability | Contribs. check for Institutions of public power of the Czech Republic took 0.17295265197753906s
Interlinking | sameAs chians check for Institutions of public power of the Czech Republic took 1.426884412765503s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.20751094818115234s
Interlinking | skos check for Institutions of public power of the Czech Republic took 0.12385821342468262s
Timeliness | dataset update frequency check for Institutions of public power of the Czech Republic took 0.298076868057251s
Currency | Creation date check for Institutions of public power of the Czech Republic took 1.0765810012817383s
Currency | Modification date check for Institutions of public power of the Czech Republic took 0.34627318382263184s
Rep.Conc. | URIs length for Institutions of public power of the Czech Republic took 243.26612043380737s
Interoperability | New vocabularies check for Institutions of public power of the Czech Republic took 81.06118583679199s
Consistency | Deprecated classes/propertiers check for Institutions of public power of the Czech Republic took 0.4721808433532715s
Accuracy | Check Functional Property for Institutions of public power of the Czech Republic took 0.23804473876953125s
Accuracy | Check Inverse Functional Property for Institutions of public power of the Czech Republic took 0.16125845909118652s
Accuracy | Check Empty annotation labels for Institutions of public power of the Czech Republic took 91.01443195343018s
Accuracy | Check White space in annotation for Institutions of public power of the Czech Republic took 3.080519437789917s
Accuracy | Check Datatype consistency for Institutions of public power of the Czech Republic took 2.610990285873413s
Consistency | Disjoint class check for Institutions of public power of the Czech Republic took 0.12685799598693848s
Consistency | Check Misplaced properties for Institutions of public power of the Czech Republic took 133.37380456924438s
Consistency | Misplaced classes for Institutions of public power of the Czech Republic took 7.829875707626343s
Consistency | Check Ontology hijacking for Institutions of public power of the Czech Republic took 82.46602320671082s
Consistency | Check Invalid usage of undefined classes for Institutions of public power of the Czech Republic took 1.4385955333709717s
Consistency | Check Invalid usage of undefined properties for Institutions of public power of the Czech Republic took 125.17493200302124s
Conciseness | Check Extensional conciseness for Institutions of public power of the Czech Republic took 2.675502061843872s
Conciseness | Check Intensional conciseness for Institutions of public power of the Czech Republic took 1.4799010753631592s
Security | Sign check for Institutions of public power of the Czech Republic took 0.16576623916625977s
Availability | Check URIs Dereferenciability for Institutions of public power of the Czech Republic took 11.309123277664185s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 1.1004855632781982s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021263599395751953s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 5.173683166503906e-05s
Interoperability | Check the re-using of existing vocabs for Institutions of public power of the Czech Republic took 76.70686149597168s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 9.775161743164062e-06s
INFO | --- Analysis for cz-ovm took 2664.3565833568573s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 0.12006235122680664s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.2540402412414551s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-ovm-agendas took 4.516499996185303s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.07896709442138672s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.25859642028808594s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.723403930664062e-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 5.043488502502441s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.7082457542419434s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.2927062511444092s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0009510517120361328s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 8.273124694824219e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 3.7540276050567627s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.4820375442504883s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.2585487365722656s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 4.5299530029296875e-06s
INFO | --- Analysis for cz-sao-check-actions took 3.5415937900543213s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 0.4848191738128662s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.2576634883880615s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.020734548568725586s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.049041748046875e-05s
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.0040740966796875e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 5.0067901611328125e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 3.5472412109375s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 0.10491752624511719s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0010721683502197266s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.28074026107788086s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020635604858398438s
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.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.2901763916015625e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.754830837249756s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.11157369613647461s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0008437633514404297s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.2701597213745117s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.170967102050781e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 4.76837158203125e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.7705345153808594s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 0.10497426986694336s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.28017663955688477s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.804290294647217s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 0.11317086219787598s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0006511211395263672s
Extra | Recovery of all triples for Summary types of Czech institutions of public power took 303.66925978660583s
Performance | Total latancy measurement for Summary types of Czech institutions of public power took 0.637066125869751s
Amount of data | Number of triples check for Summary types of Czech institutions of public power took 20.945799827575684s
Interoperability | New terms check for Summary types of Czech institutions of public power took 20.943183422088623s
Versatility | Languages check for Summary types of Czech institutions of public power took 300.14677238464355s
Interpretability | Number of blank nodes check for Summary types of Czech institutions of public power took 7.779171943664551s
Interpretability | RDF structures check for Summary types of Czech institutions of public power took 0.12310338020324707s
Versatility | Serialization formats check for Summary types of Czech institutions of public power took 0.870189905166626s
Availability | RDF dump link check for Summary types of Czech institutions of public power took 14.520471334457397s
License | MR license check for Summary types of Czech institutions of public power took 0.10224628448486328s
License | HR license check for Summary types of Czech institutions of public power took 244.7510280609131s
Amount of data | Number of property check for Summary types of Czech institutions of public power took 0.19431710243225098s
Understandability | Number of label check for Summary types of Czech institutions of public power took 9.207708358764648s
Understandability | URI regex check for Summary types of Czech institutions of public power took 0.2629842758178711s
Understandability | Vocabs check for Summary types of Czech institutions of public power took 0.16132259368896484s
Verifiability | Authors check for Summary types of Czech institutions of public power took 0.3843855857849121s
Verifiability | Publishers check for Summary types of Czech institutions of public power took 0.1710202693939209s
Performance | Throughput check for Summary types of Czech institutions of public power took 10.569420576095581s
Amount of data | Check the number of entities for Summary types of Czech institutions of public power took 3.0043797492980957s
Verifiability | Contribs. check for Summary types of Czech institutions of public power took 0.25357604026794434s
Interlinking | sameAs chians check for Summary types of Czech institutions of public power took 0.7982559204101562s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.34761691093444824s
Interlinking | skos check for Summary types of Czech institutions of public power took 0.1105048656463623s
Timeliness | dataset update frequency check for Summary types of Czech institutions of public power took 0.3547537326812744s
Currency | Creation date check for Summary types of Czech institutions of public power took 1.2537150382995605s
Currency | Modification date check for Summary types of Czech institutions of public power took 0.3975179195404053s
Rep.Conc. | URIs length for Summary types of Czech institutions of public power took 286.7809238433838s
Interoperability | New vocabularies check for Summary types of Czech institutions of public power took 116.9038999080658s
Consistency | Deprecated classes/propertiers check for Summary types of Czech institutions of public power took 0.45032644271850586s
Accuracy | Check Functional Property for Summary types of Czech institutions of public power took 0.12372612953186035s
Accuracy | Check Inverse Functional Property for Summary types of Czech institutions of public power took 0.11240029335021973s
Accuracy | Check Empty annotation labels for Summary types of Czech institutions of public power took 99.21156859397888s
Accuracy | Check White space in annotation for Summary types of Czech institutions of public power took 3.046097755432129s
Accuracy | Check Datatype consistency for Summary types of Czech institutions of public power took 2.6961350440979004s
Consistency | Disjoint class check for Summary types of Czech institutions of public power took 0.13057422637939453s
Consistency | Check Misplaced properties for Summary types of Czech institutions of public power took 133.84480452537537s
Consistency | Misplaced classes for Summary types of Czech institutions of public power took 8.072400569915771s
Consistency | Check Ontology hijacking for Summary types of Czech institutions of public power took 83.4209623336792s
Consistency | Check Invalid usage of undefined classes for Summary types of Czech institutions of public power took 1.4683985710144043s
Consistency | Check Invalid usage of undefined properties for Summary types of Czech institutions of public power took 152.5105676651001s
Conciseness | Check Extensional conciseness for Summary types of Czech institutions of public power took 2.679319381713867s
Conciseness | Check Intensional conciseness for Summary types of Czech institutions of public power took 1.696664571762085s
Security | Sign check for Summary types of Czech institutions of public power took 0.21288466453552246s
Availability | Check URIs Dereferenciability for Summary types of Czech institutions of public power took 11.31941032409668s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 1.2183849811553955s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.021002531051635742s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 4.482269287109375e-05s
Interoperability | Check the re-using of existing vocabs for Summary types of Czech institutions of public power took 69.74176454544067s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 9.059906005859375e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2625.65296792984s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 0.10407185554504395s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0008597373962402344s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.2890901565551758s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.314018249511719e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 4.487583875656128s
Availability | SPARQL endpoint availability check for State funding providers took 0.10244107246398926s
Availability | VoID file availability check for State funding providers took 0.00031185150146484375s
Completeness | Calculation of interlinking completeness for State funding providers took 0.6869626045227051s
Reputation | Calculation of the PageRank for State funding providers took 0.02037215232849121s
Interlinking | Calculation of Degree of Connection for State funding providers took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for State funding providers took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.00543212890625e-05s
Believability | Calculation of trust value for State funding providers took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 3.602729082107544s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 0.11342406272888184s
Availability | VoID file availability check for Organizations active in R&D took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.2553584575653076s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.790855407714844e-05s
Believability | Calculation of trust value for Organizations active in R&D took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.92549467086792s
Availability | SPARQL endpoint availability check for R&D Programmes took 0.1035764217376709s
Availability | VoID file availability check for R&D Programmes took 0.0007905960083007812s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.28270506858825684s
Reputation | Calculation of the PageRank for R&D Programmes took 0.020240306854248047s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.910064697265625e-05s
Believability | Calculation of trust value for R&D Programmes took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.699431896209717s
Availability | SPARQL endpoint availability check for R&D Projects took 0.10459518432617188s
Availability | VoID file availability check for R&D Projects took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.25933313369750977s
Reputation | Calculation of the PageRank for R&D Projects took 0.020402193069458008s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.220008850097656e-05s
Believability | Calculation of trust value for R&D Projects took 5.4836273193359375e-06s
INFO | --- Analysis for cz-vavai-projects took 2.765535354614258s
Availability | SPARQL endpoint availability check for Institutional research plans took 0.10811543464660645s
Availability | VoID file availability check for Institutional research plans took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2624175548553467s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020172119140625s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.910064697265625e-05s
Believability | Calculation of trust value for Institutional research plans took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.8109776973724365s
Availability | SPARQL endpoint availability check for Results of R&D took 0.10257935523986816s
Availability | VoID file availability check for Results of R&D took 0.0007517337799072266s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.2666313648223877s
Reputation | Calculation of the PageRank for Results of R&D took 0.02030467987060547s
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.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.886222839355469e-05s
Believability | Calculation of trust value for Results of R&D took 4.5299530029296875e-06s
INFO | --- Analysis for cz-vavai-results took 2.7567989826202393s
Availability | SPARQL endpoint availability check for Tenders in R&D took 0.10487866401672363s
Availability | VoID file availability check for Tenders in R&D took 0.0004048347473144531s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.24869394302368164s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 3.647804260253906e-05s
Believability | Calculation of trust value for Tenders in R&D took 5.245208740234375e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.721543550491333s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.553794860839844e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.2724621295928955s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.0040740966796875e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 6.67572021484375e-06s
INFO | --- Analysis for czech_addresses took 4.492733716964722s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 0.628903865814209s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0006618499755859375s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.28053998947143555s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020218849182128906s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for DanteLatinLoanwords took 4.035513639450073s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3933238983154297s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0005943775177001953s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 138.80884408950806s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0363571643829346s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 9.177896499633789s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.139434099197388s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.29170751571655s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.20071768760681152s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.13050293922424316s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.6692380905151367s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.35988593101501465s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.24111056327819824s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.4994010925292969s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 66.09285736083984s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.23103976249694824s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 1.429532766342163s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.523662805557251s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.21964406967163086s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.2390124797821045s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.23496222496032715s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.435940265655518s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 8.106231689453125e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.20143699645996094s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 1.3904798030853271s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.7372491359710693s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.7537338733673096s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.29453206062316895s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 0.6665213108062744s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 0.6362192630767822s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 77.91597104072571s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2579224109649658s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.38074827194213867s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.377291202545166s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 41.09326362609863s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.1978609561920166s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.608975648880005s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.5309715270996094s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.38765239715576s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.483215570449829s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 50.442702293395996s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.570155382156372s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 21.40192437171936s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.8640494346618652s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.23855900764465332s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.8892238140106201s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 9.404132604598999s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.9361028671264648s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021532773971557617s
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.000904083251953125s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001513957977294922s
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.62939453125e-06s
INFO | --- Analysis for data-bnf-fr took 761.6328032016754s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 0.2596259117126465s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0006239414215087891s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.3041188716888428s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.022324085235595703s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007984638214111328s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 7.843971252441406e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 5.4836273193359375e-06s
INFO | --- Analysis for data-cnr-it took 3.5444300174713135s
Availability | SPARQL endpoint availability check for Data.gov took 1.7402479648590088s
Availability | VoID file availability check for Data.gov took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Data.gov took 0.27367687225341797s
Reputation | Calculation of the PageRank for Data.gov took 0.02060532569885254s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.0040740966796875e-05s
Believability | Calculation of trust value for Data.gov took 5.4836273193359375e-06s
INFO | --- Analysis for data-gov took 18.181167125701904s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 0.1190650463104248s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.24477791786193848s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.866455078125e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 8.106231689453125e-06s
INFO | --- Analysis for data-gov-ie took 2.5756447315216064s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.1961669921875e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2853412628173828s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.02068495750427246s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 8.082389831542969e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 4.5299530029296875e-06s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.9116804599761963s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.669164180755615s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0006361007690429688s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.2781999111175537s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 6.151199340820312e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 6.9141387939453125e-06s
INFO | --- Analysis for data-hnm-hu took 163.4622781276703s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.20516157150268555s
Availability | VoID file availability check for Climb Dataincubator took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.6829326152801514s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020447731018066406s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.176399230957031e-05s
Believability | Calculation of trust value for Climb Dataincubator took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-climb took 3.479635715484619s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.792213439941406e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006515979766845703s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.26226234436035156s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 8.940696716308594e-05s
Believability | Calculation of trust value for Discogs in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-discogs took 7.796952247619629s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 0.057196617126464844s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.27680253982543945s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0008020401000976562s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 7.557868957519531e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 9.775161743164062e-06s
INFO | --- Analysis for data-incubator-metoffice took 7.578779935836792s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.052312612533569336s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006592273712158203s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.27005457878112793s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 9.059906005859375e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-moseley took 13.298816442489624s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.06265974044799805s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.24196529388427734s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.036064147949219e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.4264798164367676s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 1.8644473552703857s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.0006735324859619141s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.2751030921936035s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.225440979003906e-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 7.127656698226929s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 0.23546338081359863s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.25745248794555664s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.319450378417969e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.6172702312469482s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 0.06450772285461426s
Availability | VoID file availability check for Pokedex data in RDF took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2552919387817383s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.179115295410156e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-pokedex took 3.3177602291107178s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.060691118240356445s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.27303647994995117s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.022197961807250977s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0011410713195800781s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 0.0001220703125s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 7.867813110351562e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.4827775955200195s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 121.25842332839966s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0009636878967285156s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.9228997230529785s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 7.939338684082031e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 6.9141387939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 680.1112117767334s
Availability | SPARQL endpoint availability check for Persée in RDF took 0.8061964511871338s
Availability | VoID file availability check for Persée in RDF took 0.0007069110870361328s
Extra | Recovery of all triples for Persée in RDF took 3.1973750591278076s
Performance | Total latancy measurement for Persée in RDF took 1.5138664245605469s
Amount of data | Number of triples check for Persée in RDF took 1.097285270690918s
Interoperability | New terms check for Persée in RDF took 2.0432238578796387s
Versatility | Languages check for Persée in RDF took 121.00561213493347s
Interpretability | Number of blank nodes check for Persée in RDF took 0.4367990493774414s
Interpretability | RDF structures check for Persée in RDF took 0.8310127258300781s
Versatility | Serialization formats check for Persée in RDF took 1.019209384918213s
Availability | RDF dump link check for Persée in RDF took 0.30646347999572754s
License | MR license check for Persée in RDF took 1.542858600616455s
License | HR license check for Persée in RDF took 38.595577239990234s
Amount of data | Number of property check for Persée in RDF took 0.12048888206481934s
Understandability | Number of label check for Persée in RDF took 2.116982936859131s
Understandability | URI regex check for Persée in RDF took 0.9048590660095215s
Understandability | Vocabs check for Persée in RDF took 0.4336888790130615s
Verifiability | Authors check for Persée in RDF took 0.18743586540222168s
Verifiability | Publishers check for Persée in RDF took 0.1347980499267578s
Performance | Throughput check for Persée in RDF took 10.753090858459473s
Amount of data | Check the number of entities for Persée in RDF took 7.033348083496094e-05s
Verifiability | Contribs. check for Persée in RDF took 0.14532136917114258s
Interlinking | sameAs chians check for Persée in RDF took 0.3811779022216797s
Interlinking | skos check for Persée in RDF took 0.7507460117340088s
Interlinking | skos check for Persée in RDF took 0.15021133422851562s
Timeliness | dataset update frequency check for Persée in RDF took 0.7347958087921143s
Currency | Creation date check for Persée in RDF took 0.5518717765808105s
Currency | Modification date check for Persée in RDF took 0.2814195156097412s
Rep.Conc. | URIs length for Persée in RDF took 3.578805923461914s
Interoperability | New vocabularies check for Persée in RDF took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Persée in RDF took 0.14546513557434082s
Accuracy | Check Functional Property for Persée in RDF took 0.15917134284973145s
Accuracy | Check Inverse Functional Property for Persée in RDF took 0.13103628158569336s
Accuracy | Check Empty annotation labels for Persée in RDF took 1.0527071952819824s
Accuracy | Check White space in annotation for Persée in RDF took 0.0378720760345459s
Accuracy | Check Datatype consistency for Persée in RDF took 0.027968883514404297s
Consistency | Disjoint class check for Persée in RDF took 0.21944952011108398s
Consistency | Check Misplaced properties for Persée in RDF took 2.583714246749878s
Consistency | Misplaced classes for Persée in RDF took 0.21977782249450684s
Consistency | Check Ontology hijacking for Persée in RDF took 1.9851653575897217s
Consistency | Check Invalid usage of undefined classes for Persée in RDF took 1.2729871273040771s
Consistency | Check Invalid usage of undefined properties for Persée in RDF took 3.7920982837677s
Conciseness | Check Extensional conciseness for Persée in RDF took 0.033008575439453125s
Conciseness | Check Intensional conciseness for Persée in RDF took 0.15662455558776855s
Security | Sign check for Persée in RDF took 0.8530762195587158s
Availability | Check URIs Dereferenciability for Persée in RDF took 1331.0492079257965s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.8361005783081055s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011420249938964844s
Interoperability | Check the re-using of existing vocabs for Persée in RDF took 1.430511474609375e-06s
Believability | Calculation of trust value for Persée in RDF took 8.106231689453125e-06s
INFO | --- Analysis for data-persee-fr took 1579.7313759326935s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.100799560546875e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.2506852149963379s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020217180252075195s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 2.9325485229492188e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 6.9141387939453125e-06s
INFO | --- Analysis for data-southampton-ac-uk took 3.8591928482055664s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 0.8314793109893799s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0005991458892822266s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.254321813583374s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011014938354492188s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 6.67572021484375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 9.420465469360352s
Availability | SPARQL endpoint availability check for Open Data Web took 0.5893983840942383s
Availability | VoID file availability check for Open Data Web took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.2422494888305664s
Reputation | Calculation of the PageRank for Open Data Web took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Data Web took 7.3909759521484375e-06s
INFO | --- Analysis for data.odw.tw took 3.4094297885894775s
Availability | SPARQL endpoint availability check for DataFAQs took 4.1484832763671875e-05s
Availability | VoID file availability check for DataFAQs took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.2506883144378662s
Reputation | Calculation of the PageRank for DataFAQs took 0.020348548889160156s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 2.9325485229492188e-05s
Believability | Calculation of trust value for DataFAQs took 6.9141387939453125e-06s
INFO | --- Analysis for datafaqs took 3.3016438484191895s
Availability | SPARQL endpoint availability check for datahub took 4.172325134277344e-05s
Availability | VoID file availability check for datahub took 0.0006506443023681641s
Completeness | Calculation of interlinking completeness for datahub took 0.2559056282043457s
Reputation | Calculation of the PageRank for datahub took 0.020089387893676758s
Interlinking | Calculation of Degree of Connection for datahub took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for datahub took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for datahub took 4.3392181396484375e-05s
Believability | Calculation of trust value for datahub took 6.198883056640625e-06s
INFO | --- Analysis for datahub took 5.025811433792114s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 5.953136444091797s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0011792182922363281s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.24040436744689941s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0013580322265625e-05s
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 2.9325485229492188e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 7.152557373046875e-06s
INFO | --- Analysis for datahub-kr-datamap took 15.789822816848755s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.47394537925720215s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.3829479217529297s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.02040410041809082s
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.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.985664367675781e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.67572021484375e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 5.812102317810059s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.216297388076782s
Availability | VoID file availability check for datos-artium-org took 0.0008111000061035156s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.412264347076416s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020874500274658203s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00012540817260742188s
Believability | Calculation of trust value for datos-artium-org took 1.1682510375976562e-05s
INFO | --- Analysis for datos-artium-org took 164.8919553756714s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 1.839550495147705s
Availability | VoID file availability check for Datos.bcn.cl took 0.0007231235504150391s
Extra | Recovery of all triples for Datos.bcn.cl took 163.83255577087402s
Performance | Total latancy measurement for Datos.bcn.cl took 263.70650577545166s
Amount of data | Number of triples check for Datos.bcn.cl took 64.8372962474823s
Interoperability | New terms check for Datos.bcn.cl took 62.74575233459473s
Versatility | Languages check for Datos.bcn.cl took 301.0079855918884s
Interpretability | Number of blank nodes check for Datos.bcn.cl took 1.3797123432159424s
Security | Check HTTPS for Datos.bcn.cl took 62.37966251373291s
Interpretability | RDF structures check for Datos.bcn.cl took 62.68464946746826s
Versatility | Serialization formats check for Datos.bcn.cl took 62.41891574859619s
Availability | RDF dump link check for Datos.bcn.cl took 62.50082612037659s
License | MR license check for Datos.bcn.cl took 62.541900396347046s
License | HR license check for Datos.bcn.cl took 94.34740471839905s
Amount of data | Number of property check for Datos.bcn.cl took 30.777977228164673s
Understandability | Number of label check for Datos.bcn.cl took 63.03582262992859s
Understandability | URI regex check for Datos.bcn.cl took 124.47139811515808s
Understandability | Vocabs check for Datos.bcn.cl took 62.54694151878357s
Verifiability | Authors check for Datos.bcn.cl took 62.49930930137634s
Verifiability | Publishers check for Datos.bcn.cl took 62.51391839981079s
Performance | Throughput check for Datos.bcn.cl took 625.2580015659332s
Amount of data | Check the number of entities for Datos.bcn.cl took 7.581710815429688e-05s
Verifiability | Contribs. check for Datos.bcn.cl took 62.53345990180969s
Interlinking | sameAs chians check for Datos.bcn.cl took 62.60898399353027s
Interlinking | skos check for Datos.bcn.cl took 62.47807025909424s
Interlinking | skos check for Datos.bcn.cl took 62.498024702072144s
Timeliness | dataset update frequency check for Datos.bcn.cl took 62.553953886032104s
Currency | Creation date check for Datos.bcn.cl took 125.06781268119812s
Currency | Modification date check for Datos.bcn.cl took 62.531612157821655s
Rep.Conc. | URIs length for Datos.bcn.cl took 138.24241971969604s
Interoperability | New vocabularies check for Datos.bcn.cl took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Datos.bcn.cl took 49.27379512786865s
Accuracy | Check Functional Property for Datos.bcn.cl took 62.503859758377075s
Accuracy | Check Inverse Functional Property for Datos.bcn.cl took 62.54460000991821s
Accuracy | Check Empty annotation labels for Datos.bcn.cl took 72.37320041656494s
Accuracy | Check White space in annotation for Datos.bcn.cl took 0.23846936225891113s
Accuracy | Check Datatype consistency for Datos.bcn.cl took 0.26337695121765137s
Consistency | Disjoint class check for Datos.bcn.cl took 52.21406626701355s
Consistency | Check Misplaced properties for Datos.bcn.cl took 129.02309894561768s
Consistency | Misplaced classes for Datos.bcn.cl took 59.377177000045776s
Consistency | Check Ontology hijacking for Datos.bcn.cl took 71.61734652519226s
Consistency | Check Invalid usage of undefined classes for Datos.bcn.cl took 1.356008768081665s
Consistency | Check Invalid usage of undefined properties for Datos.bcn.cl took 56.341145277023315s
Conciseness | Check Extensional conciseness for Datos.bcn.cl took 0.30254626274108887s
Conciseness | Check Intensional conciseness for Datos.bcn.cl took 57.38340735435486s
Security | Sign check for Datos.bcn.cl took 62.26978850364685s
Availability | Check URIs Dereferenciability for Datos.bcn.cl took 12.062196254730225s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 1.174856424331665s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.021038532257080078s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.700920104980469e-05s
Interoperability | Check the re-using of existing vocabs for Datos.bcn.cl took 1.9073486328125e-06s
Believability | Calculation of trust value for Datos.bcn.cl took 6.198883056640625e-06s
INFO | --- Analysis for datos-bcn-cl took 5813.116137504578s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.415224552154541s
Availability | VoID file availability check for datos.bne.es took 0.0006308555603027344s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.7205970287322998s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011157989501953125s
Believability | Calculation of trust value for datos.bne.es took 7.152557373046875e-06s
INFO | --- Analysis for datos-bne-es took 6.7980523109436035s
Availability | SPARQL endpoint availability check for dbacademic took 0.47115230560302734s
Availability | VoID file availability check for dbacademic took 0.0003631114959716797s
Completeness | Calculation of interlinking completeness for dbacademic took 0.2716104984283447s
Reputation | Calculation of the PageRank for dbacademic took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for dbacademic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dbacademic took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.62396240234375e-05s
Believability | Calculation of trust value for dbacademic took 5.0067901611328125e-06s
INFO | --- Analysis for dbacademic took 2.884413003921509s
Availability | SPARQL endpoint availability check for DBkWik took 124.23749375343323s
Availability | VoID file availability check for DBkWik took 0.0008192062377929688s
Extra | Recovery of all triples for DBkWik took 2.8761911392211914s
Performance | Total latancy measurement for DBkWik took 0.4320952892303467s
Amount of data | Number of triples check for DBkWik took 7.618764162063599s
Interoperability | New terms check for DBkWik took 2.1558308601379395s
Versatility | Languages check for DBkWik took 60.891040563583374s
Interpretability | Number of blank nodes check for DBkWik took 0.14025354385375977s
Interpretability | RDF structures check for DBkWik took 0.21969938278198242s
Versatility | Serialization formats check for DBkWik took 0.2891499996185303s
Availability | RDF dump link check for DBkWik took 2.9180712699890137s
License | MR license check for DBkWik took 0.268169641494751s
License | HR license check for DBkWik took 106.64418244361877s
Amount of data | Number of property check for DBkWik took 5.0313496589660645s
Understandability | Number of label check for DBkWik took 5.703022480010986s
Understandability | URI regex check for DBkWik took 1.691694974899292s
Understandability | Vocabs check for DBkWik took 0.5955538749694824s
Verifiability | Authors check for DBkWik took 0.8898978233337402s
Verifiability | Publishers check for DBkWik took 0.7230236530303955s
Performance | Throughput check for DBkWik took 10.496317863464355s
Amount of data | Check the number of entities for DBkWik took 8.416175842285156e-05s
Verifiability | Contribs. check for DBkWik took 0.10900354385375977s
Interlinking | sameAs chians check for DBkWik took 0.41878318786621094s
Interlinking | skos check for DBkWik took 0.5491552352905273s
Interlinking | skos check for DBkWik took 0.0757756233215332s
Timeliness | dataset update frequency check for DBkWik took 0.21144461631774902s
Currency | Creation date check for DBkWik took 0.45180535316467285s
Currency | Modification date check for DBkWik took 0.21173310279846191s
Rep.Conc. | URIs length for DBkWik took 12.020694494247437s
Interoperability | New vocabularies check for DBkWik took 17.18560242652893s
Consistency | Deprecated classes/propertiers check for DBkWik took 4.923183917999268s
Accuracy | Check Functional Property for DBkWik took 5.735112428665161s
Accuracy | Check Inverse Functional Property for DBkWik took 4.343280553817749s
Accuracy | Check Empty annotation labels for DBkWik took 6.188469171524048s
Accuracy | Check White space in annotation for DBkWik took 0.02326178550720215s
Accuracy | Check Datatype consistency for DBkWik took 0.02725672721862793s
Consistency | Disjoint class check for DBkWik took 1.668949842453003s
Consistency | Check Misplaced properties for DBkWik took 14.155319929122925s
Consistency | Misplaced classes for DBkWik took 0.6786935329437256s
Consistency | Check Ontology hijacking for DBkWik took 2.752549648284912s
Consistency | Check Invalid usage of undefined classes for DBkWik took 1.3378543853759766s
Consistency | Check Invalid usage of undefined properties for DBkWik took 11.737861633300781s
Conciseness | Check Extensional conciseness for DBkWik took 0.032805681228637695s
Conciseness | Check Intensional conciseness for DBkWik took 2.334199905395508s
Security | Sign check for DBkWik took 1.137751579284668s
Availability | Check URIs Dereferenciability for DBkWik took 12.68088173866272s
Completeness | Calculation of interlinking completeness for DBkWik took 0.3752129077911377s
Reputation | Calculation of the PageRank for DBkWik took 0.19039392471313477s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for DBkWik took 8.177757263183594e-05s
Interoperability | Check the re-using of existing vocabs for DBkWik took 22.880242347717285s
Believability | Calculation of trust value for DBkWik took 7.3909759521484375e-06s
INFO | --- Analysis for dbkwik took 1677.2834599018097s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.363059997558594e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.2908897399902344s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001361370086669922s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 16.336262464523315s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 0.32904791831970215s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0005753040313720703s
Extra | Recovery of all triples for dblp Knowledge Graph took 7.492455959320068s
Performance | Total latancy measurement for dblp Knowledge Graph took 0.7059733867645264s
Amount of data | Number of triples check for dblp Knowledge Graph took 0.13607144355773926s
Interoperability | New terms check for dblp Knowledge Graph took 1.8640995025634766s
Versatility | Languages check for dblp Knowledge Graph took 33.6353702545166s
Interpretability | Number of blank nodes check for dblp Knowledge Graph took 2.1235733032226562s
Interpretability | RDF structures check for dblp Knowledge Graph took 0.1671161651611328s
Versatility | Serialization formats check for dblp Knowledge Graph took 0.15030169486999512s
Availability | RDF dump link check for dblp Knowledge Graph took 0.1233828067779541s
License | MR license check for dblp Knowledge Graph took 0.14706993103027344s
License | HR license check for dblp Knowledge Graph took 30.142667055130005s
Amount of data | Number of property check for dblp Knowledge Graph took 1.1338956356048584s
Understandability | Number of label check for dblp Knowledge Graph took 0.5075268745422363s
Understandability | URI regex check for dblp Knowledge Graph took 0.2573084831237793s
Understandability | Vocabs check for dblp Knowledge Graph took 0.14188313484191895s
Verifiability | Authors check for dblp Knowledge Graph took 0.1223764419555664s
Verifiability | Publishers check for dblp Knowledge Graph took 0.12679719924926758s
Performance | Throughput check for dblp Knowledge Graph took 10.767379760742188s
Amount of data | Check the number of entities for dblp Knowledge Graph took 7.271766662597656e-05s
Verifiability | Contribs. check for dblp Knowledge Graph took 0.11886000633239746s
Interlinking | sameAs chians check for dblp Knowledge Graph took 0.17107462882995605s
Interlinking | skos check for dblp Knowledge Graph took 0.13955354690551758s
Interlinking | skos check for dblp Knowledge Graph took 0.13571977615356445s
Timeliness | dataset update frequency check for dblp Knowledge Graph took 0.12351727485656738s
Currency | Creation date check for dblp Knowledge Graph took 0.3362140655517578s
Currency | Modification date check for dblp Knowledge Graph took 0.30670690536499023s
Rep.Conc. | URIs length for dblp Knowledge Graph took 15.210956811904907s
Interoperability | New vocabularies check for dblp Knowledge Graph took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for dblp Knowledge Graph took 0.13808894157409668s
Accuracy | Check Functional Property for dblp Knowledge Graph took 0.1579282283782959s
Accuracy | Check Inverse Functional Property for dblp Knowledge Graph took 0.15807247161865234s
Accuracy | Check Empty annotation labels for dblp Knowledge Graph took 6.843358039855957s
Accuracy | Check White space in annotation for dblp Knowledge Graph took 3.079545736312866s
Accuracy | Check Datatype consistency for dblp Knowledge Graph took 6.1605751514434814s
Consistency | Disjoint class check for dblp Knowledge Graph took 0.14699888229370117s
Consistency | Check Misplaced properties for dblp Knowledge Graph took 0.27932047843933105s
Consistency | Check Ontology hijacking for dblp Knowledge Graph took 5.452419996261597s
Consistency | Check Invalid usage of undefined classes for dblp Knowledge Graph took 17929.376396656036s
Consistency | Check Invalid usage of undefined properties for dblp Knowledge Graph took 4.643345355987549s
Conciseness | Check Extensional conciseness for dblp Knowledge Graph took 2.704619884490967s
Conciseness | Check Intensional conciseness for dblp Knowledge Graph took 0.1553974151611328s
Security | Sign check for dblp Knowledge Graph took 0.15147185325622559s
Availability | Check URIs Dereferenciability for dblp Knowledge Graph took 2.348529100418091s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 1.5700688362121582s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021519899368286133s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for dblp Knowledge Graph took 2.1457672119140625e-06s
Believability | Calculation of trust value for dblp Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for dblp-kg took 18150.280826568604s
Availability | SPARQL endpoint availability check for dbnary took 0.3148314952850342s
Availability | VoID file availability check for dbnary took 0.0005040168762207031s
Extra | Recovery of all triples for dbnary took 1.9541819095611572s
Performance | Total latancy measurement for dbnary took 0.3769550323486328s
Amount of data | Number of triples check for dbnary took 1.2177715301513672s
Interoperability | New terms check for dbnary took 3.692293882369995s
Versatility | Languages check for dbnary took 61.95814394950867s
Interpretability | Number of blank nodes check for dbnary took 3.701986074447632s
Security | Check HTTPS for dbnary took 0.17444872856140137s
Interpretability | RDF structures check for dbnary took 0.11858391761779785s
Versatility | Serialization formats check for dbnary took 0.8029077053070068s
Availability | RDF dump link check for dbnary took 0.11129140853881836s
License | MR license check for dbnary took 0.1238858699798584s
License | HR license check for dbnary took 61.9933602809906s
Amount of data | Number of property check for dbnary took 0.10334467887878418s
Understandability | Number of label check for dbnary took 1.2383127212524414s
Understandability | URI regex check for dbnary took 0.20270037651062012s
Understandability | Vocabs check for dbnary took 0.7328314781188965s
Verifiability | Authors check for dbnary took 0.08839178085327148s
Verifiability | Publishers check for dbnary took 0.10560417175292969s
Performance | Throughput check for dbnary took 10.336301803588867s
Amount of data | Check the number of entities for dbnary took 8.082389831542969e-05s
Verifiability | Contribs. check for dbnary took 0.0723111629486084s
Interlinking | sameAs chians check for dbnary took 0.09442806243896484s
Interlinking | skos check for dbnary took 1.6832244396209717s
Interlinking | skos check for dbnary took 0.07906889915466309s
Timeliness | dataset update frequency check for dbnary took 0.22345948219299316s
Currency | Creation date check for dbnary took 0.17546296119689941s
Currency | Modification date check for dbnary took 0.17214584350585938s
Rep.Conc. | URIs length for dbnary took 11.46606159210205s
Interoperability | New vocabularies check for dbnary took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for dbnary took 0.09438657760620117s
Accuracy | Check Functional Property for dbnary took 0.1535964012145996s
Accuracy | Check Inverse Functional Property for dbnary took 0.14981555938720703s
Accuracy | Check Empty annotation labels for dbnary took 0.4571549892425537s
Accuracy | Check White space in annotation for dbnary took 0.02533411979675293s
Accuracy | Check Datatype consistency for dbnary took 0.02699756622314453s
Consistency | Disjoint class check for dbnary took 0.10101509094238281s
Consistency | Check Misplaced properties for dbnary took 8.844785928726196s
Consistency | Misplaced classes for dbnary took 0.2357797622680664s
Consistency | Check Ontology hijacking for dbnary took 1.945446491241455s
Consistency | Check Invalid usage of undefined classes for dbnary took 1.3459758758544922s
Consistency | Check Invalid usage of undefined properties for dbnary took 10.037545680999756s
Conciseness | Check Extensional conciseness for dbnary took 0.03167581558227539s
Conciseness | Check Intensional conciseness for dbnary took 0.1648271083831787s
Security | Sign check for dbnary took 0.08733153343200684s
Availability | Check URIs Dereferenciability for dbnary took 11.074828386306763s
Completeness | Calculation of interlinking completeness for dbnary took 0.6946721076965332s
Reputation | Calculation of the PageRank for dbnary took 0.02079010009765625s
Interlinking | Calculation of Degree of Connection for dbnary took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for dbnary took 5.53131103515625e-05s
Interoperability | Check the re-using of existing vocabs for dbnary took 1.6689300537109375e-06s
Believability | Calculation of trust value for dbnary took 7.3909759521484375e-06s
INFO | --- Analysis for dbnary took 307.4293293952942s
Availability | SPARQL endpoint availability check for DBpedia took 0.4521911144256592s
Availability | VoID file availability check for DBpedia took 0.0006089210510253906s
Extra | Recovery of all triples for DBpedia took 17.45986294746399s
Performance | Total latancy measurement for DBpedia took 0.9734518527984619s
Amount of data | Number of triples check for DBpedia took 0.710939884185791s
Interoperability | New terms check for DBpedia took 5.749034404754639s
Versatility | Languages check for DBpedia took 31.09750509262085s
Interpretability | Number of blank nodes check for DBpedia took 0.24203944206237793s
Security | Check HTTPS for DBpedia took 0.12506866455078125s
Interpretability | RDF structures check for DBpedia took 0.3553776741027832s
Versatility | Serialization formats check for DBpedia took 0.2566499710083008s
Availability | RDF dump link check for DBpedia took 0.24852585792541504s
License | MR license check for DBpedia took 1.1781361103057861s
License | HR license check for DBpedia took 30.565932750701904s
Amount of data | Number of property check for DBpedia took 0.2223646640777588s
Understandability | Number of label check for DBpedia took 3.2178027629852295s
Understandability | URI regex check for DBpedia took 0.6643967628479004s
Understandability | Vocabs check for DBpedia took 0.4002678394317627s
Verifiability | Authors check for DBpedia took 0.3637373447418213s
Verifiability | Publishers check for DBpedia took 0.21057987213134766s
Performance | Throughput check for DBpedia took 17.990811824798584s
Amount of data | Check the number of entities for DBpedia took 7.2479248046875e-05s
Verifiability | Contribs. check for DBpedia took 0.35071539878845215s
Interlinking | sameAs chians check for DBpedia took 2.2684316635131836s
Interlinking | skos check for DBpedia took 0.5748336315155029s
Interlinking | skos check for DBpedia took 0.22050118446350098s
Timeliness | dataset update frequency check for DBpedia took 0.28783750534057617s
Currency | Creation date check for DBpedia took 0.5986366271972656s
Currency | Modification date check for DBpedia took 0.5164694786071777s
Rep.Conc. | URIs length for DBpedia took 42.74910759925842s
Interoperability | New vocabularies check for DBpedia took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for DBpedia took 0.2114715576171875s
Accuracy | Check Functional Property for DBpedia took 0.3237137794494629s
Accuracy | Check Inverse Functional Property for DBpedia took 0.34717464447021484s
Accuracy | Check Empty annotation labels for DBpedia took 2.696570873260498s
Accuracy | Check White space in annotation for DBpedia took 0.031252384185791016s
Accuracy | Check Datatype consistency for DBpedia took 0.028292179107666016s
Consistency | Disjoint class check for DBpedia took 0.3107607364654541s
Consistency | Check Misplaced properties for DBpedia took 31.69342350959778s
Consistency | Misplaced classes for DBpedia took 0.8462553024291992s
Consistency | Check Ontology hijacking for DBpedia took 2.230001926422119s
Consistency | Check Invalid usage of undefined classes for DBpedia took 1.2947626113891602s
Consistency | Check Invalid usage of undefined properties for DBpedia took 1.789994716644287s
Conciseness | Check Extensional conciseness for DBpedia took 0.03185701370239258s
Conciseness | Check Intensional conciseness for DBpedia took 2.8355448246002197s
Security | Sign check for DBpedia took 0.20769858360290527s
Availability | Check URIs Dereferenciability for DBpedia took 7575.611429929733s
Completeness | Calculation of interlinking completeness for DBpedia took 1.2125177383422852s
Reputation | Calculation of the PageRank for DBpedia took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008988380432128906s
Interoperability | Check the re-using of existing vocabs for DBpedia took 1.430511474609375e-06s
Believability | Calculation of trust value for DBpedia took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia took 8303.166579961777s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.673004150390625e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.26028895378112793s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020634889602661133s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 7.534027099609375e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 9.339749336242676s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.180734395980835s
Availability | VoID file availability check for DBpedia Commons took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.251417875289917s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.699562072753906e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-commons took 15.494787216186523s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.291534423828125e-05s
Availability | VoID file availability check for DBpedia in German took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.2574896812438965s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020328044891357422s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.556510925292969e-05s
Believability | Calculation of trust value for DBpedia in German took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-de took 4.245025157928467s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 10.889855861663818s
Availability | VoID file availability check for DBpedia in Greek took 0.0007181167602539062s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2777540683746338s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020539045333862305s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.0002040863037109375s
Believability | Calculation of trust value for DBpedia in Greek took 4.5299530029296875e-06s
INFO | --- Analysis for dbpedia-el took 47.18362617492676s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 6.5347864627838135s
Availability | VoID file availability check for DBpedia in Spanish took 0.0005812644958496094s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.2727823257446289s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020667314529418945s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010395050048828125s
Believability | Calculation of trust value for DBpedia in Spanish took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-es took 27.986106634140015s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 1.184544324874878s
Availability | VoID file availability check for DBpedia in Basque took 0.0005795955657958984s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.6997640132904053s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.0517578125e-05s
Believability | Calculation of trust value for DBpedia in Basque took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-eu took 7.3636534214019775s
Availability | SPARQL endpoint availability check for DBpedia in French took 98.58175349235535s
Availability | VoID file availability check for DBpedia in French took 0.0007393360137939453s
Extra | Recovery of all triples for DBpedia in French took 244.46934342384338s
Amount of data | Number of triples check for DBpedia in French took 90.62402582168579s
Versatility | Languages check for DBpedia in French took 10.000338315963745s
Interpretability | Number of blank nodes check for DBpedia in French took 9.999808311462402s
Interpretability | RDF structures check for DBpedia in French took 10.000084638595581s
Versatility | Serialization formats check for DBpedia in French took 71.77948951721191s
Availability | RDF dump link check for DBpedia in French took 9.999197721481323s
License | MR license check for DBpedia in French took 10.002504825592041s
License | HR license check for DBpedia in French took 300.0674350261688s
Amount of data | Number of property check for DBpedia in French took 10.031383991241455s
Understandability | Number of label check for DBpedia in French took 81.93815302848816s
Understandability | URI regex check for DBpedia in French took 88.26228284835815s
Understandability | Vocabs check for DBpedia in French took 9.999503135681152s
Verifiability | Authors check for DBpedia in French took 10.000017642974854s
Verifiability | Publishers check for DBpedia in French took 128.2962257862091s
Amount of data | Check the number of entities for DBpedia in French took 9.036064147949219e-05s
Verifiability | Contribs. check for DBpedia in French took 10.018754959106445s
Interlinking | sameAs chians check for DBpedia in French took 58.98524284362793s
Interlinking | skos check for DBpedia in French took 73.65406608581543s
Interlinking | skos check for DBpedia in French took 52.68053913116455s
Timeliness | dataset update frequency check for DBpedia in French took 55.52672529220581s
Currency | Creation date check for DBpedia in French took 20.0593364238739s
Currency | Modification date check for DBpedia in French took 20.095086336135864s
Rep.Conc. | URIs length for DBpedia in French took 19.998106241226196s
Interoperability | New vocabularies check for DBpedia in French took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for DBpedia in French took 10.100723266601562s
Accuracy | Check Functional Property for DBpedia in French took 53.48784589767456s
Accuracy | Check Inverse Functional Property for DBpedia in French took 126.03501653671265s
Accuracy | Check Empty annotation labels for DBpedia in French took 156.41850066184998s
Accuracy | Check White space in annotation for DBpedia in French took 3.0560696125030518s
Consistency | Disjoint class check for DBpedia in French took 83.7886483669281s
Consistency | Check Ontology hijacking for DBpedia in French took 104.80039429664612s
Consistency | Check Invalid usage of undefined properties for DBpedia in French took 11.314920902252197s
Conciseness | Check Extensional conciseness for DBpedia in French took 0.00017595291137695312s
Conciseness | Check Intensional conciseness for DBpedia in French took 57.491358280181885s
Security | Sign check for DBpedia in French took 10.092754364013672s
Availability | Check URIs Dereferenciability for DBpedia in French took 4798.728577375412s
Completeness | Calculation of interlinking completeness for DBpedia in French took 1.1381549835205078s
Reputation | Calculation of the PageRank for DBpedia in French took 0.0253450870513916s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 9.870529174804688e-05s
Interoperability | Check the re-using of existing vocabs for DBpedia in French took 7.152557373046875e-07s
Believability | Calculation of trust value for DBpedia in French took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-fr took 8013.1309151649475s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 4.6063456535339355s
Availability | VoID file availability check for DBpedia in Japanese took 4.0875468254089355s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.7025017738342285s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 0.0001068115234375s
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 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-ja took 39.89159917831421s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.458427429199219e-05s
Availability | VoID file availability check for dbpedia lite took 0.0006403923034667969s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.6874356269836426s
Reputation | Calculation of the PageRank for dbpedia lite took 0.02052450180053711s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.846687316894531e-05s
Believability | Calculation of trust value for dbpedia lite took 5.0067901611328125e-06s
INFO | --- Analysis for dbpedia-lite took 23.658888578414917s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.363059997558594e-05s
Availability | VoID file availability check for DBpedia-Live took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.7390995025634766s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.0994415283203125e-05s
Believability | Calculation of trust value for DBpedia-Live took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-live took 3.554098606109619s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 0.273360013961792s
Availability | VoID file availability check for DBpedia in Dutch took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2765800952911377s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001633167266845703s
Believability | Calculation of trust value for DBpedia in Dutch took 4.76837158203125e-06s
INFO | --- Analysis for dbpedia-nl took 3.27311635017395s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 0.5602285861968994s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0006928443908691406s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.2520761489868164s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 8.58306884765625e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 8.821487426757812e-06s
INFO | --- Analysis for dbpedia-pt took 4.370473623275757s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 5.459785461425781e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.26168298721313477s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.147125244140625e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 7.867813110351562e-06s
INFO | --- Analysis for dbpedia-spotlight took 2.9654805660247803s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 7.915496826171875e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0007171630859375s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.27508068084716797s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020550012588500977s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 7.104873657226562e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.2159347534179688e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 13.846968173980713s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 4.5299530029296875e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.29300951957702637s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.075599670410156e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 9.298324584960938e-06s
INFO | --- Analysis for dbpedia-wikidata took 3.346174955368042s
Availability | SPARQL endpoint availability check for DBpedia took 4.458427429199219e-05s
Availability | VoID file availability check for DBpedia took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for DBpedia took 0.26662325859069824s
Reputation | Calculation of the PageRank for DBpedia took 0.02031707763671875s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.86102294921875e-05s
Believability | Calculation of trust value for DBpedia took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia_ took 3.1679530143737793s
Availability | SPARQL endpoint availability check for DBTropes took 4.315376281738281e-05s
Availability | VoID file availability check for DBTropes took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for DBTropes took 0.24773216247558594s
Reputation | Calculation of the PageRank for DBTropes took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for DBTropes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBTropes took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for DBTropes took 8.893013000488281e-05s
Believability | Calculation of trust value for DBTropes took 6.9141387939453125e-06s
INFO | --- Analysis for dbtropes took 3.034790277481079s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 8.678436279296875e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.26548051834106445s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.9577484130859375e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 7.867813110351562e-06s
INFO | --- Analysis for dbtune took 2.862278699874878s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 5.698204040527344e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0006232261657714844s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.2670414447784424s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020865440368652344s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0009942054748535156s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 6.556510925292969e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 8.647746324539185s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 5.459785461425781e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0006136894226074219s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.28092074394226074s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02086186408996582s
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.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.4809112548828125e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.62939453125e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 5.92804479598999s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 6.732825994491577s
Availability | VoID file availability check for DBTune.org/classical took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.291426420211792s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 7.581710815429688e-05s
Believability | Calculation of trust value for DBTune.org/classical took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-classical took 22.289424896240234s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.298474311828613s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0007622241973876953s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.2643125057220459s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.021405935287475586s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 7.367134094238281e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 8.106231689453125e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 28.186652421951294s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.320430755615234s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0007200241088867188s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.28510093688964844s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 7.033348083496094e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 8.344650268554688e-06s
INFO | --- Analysis for dbtune-magnatune took 24.432408571243286s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.311014890670776s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0006251335144042969s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.2795674800872803s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011205673217773438s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.52587890625e-05s
INFO | --- Analysis for dbtune-musicbrainz took 23.873566150665283s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.308879375457764s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.3390474319458008s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.245208740234375e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-myspace took 17.907002925872803s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.220008850097656e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2713181972503662s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.0040740966796875e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 7.62939453125e-06s
INFO | --- Analysis for dclg-openuplabs took 2.9386444091796875s
Availability | SPARQL endpoint availability check for data.dcs took 4.410743713378906e-05s
Availability | VoID file availability check for data.dcs took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for data.dcs took 0.2555058002471924s
Reputation | Calculation of the PageRank for data.dcs took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for data.dcs took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for data.dcs took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.651878356933594e-05s
Believability | Calculation of trust value for data.dcs took 7.62939453125e-06s
INFO | --- Analysis for dcs-sheffield took 2.4698150157928467s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.124641418457031e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.280698299407959s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007402896881103516s
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 8.106231689453125e-06s
INFO | --- Analysis for de-budget took 2.884624719619751s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.291534423828125e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005924701690673828s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.26866888999938965s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.719329833984375e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 6.9141387939453125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 4.356433629989624s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 4.2438507080078125e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0007131099700927734s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.29892826080322266s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.458427429199219e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 7.62939453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 4.576339960098267s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.462501525878906e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.23737835884094238s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 2.8371810913085938e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.942500352859497s
Availability | SPARQL endpoint availability check for Demografie took 7.033348083496094e-05s
Availability | VoID file availability check for Demografie took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Demografie took 0.2612323760986328s
Reputation | Calculation of the PageRank for Demografie took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for Demografie took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Demografie took 0.0008053779602050781s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.956390380859375e-05s
Believability | Calculation of trust value for Demografie took 7.152557373046875e-06s
INFO | --- Analysis for demografie took 2.9635491371154785s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 4.2438507080078125e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.2749631404876709s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020551443099975586s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.8623809814453125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 6.9141387939453125e-06s
INFO | --- Analysis for desaparecidos took 2.9306702613830566s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.220008850097656e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.28228330612182617s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020322561264038086s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.918212890625e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 6.9141387939453125e-06s
INFO | --- Analysis for deustoentrepreneurship took 4.488205432891846s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.553794860839844e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.00041294097900390625s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.27065086364746094s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010585784912109375s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 6.9141387939453125e-06s
INFO | --- Analysis for deustotech took 5.739366292953491s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3837225437164307s
Availability | VoID file availability check for Deutsche Biographie took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.27118659019470215s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.021645307540893555s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.076957702636719e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.3909759521484375e-06s
INFO | --- Analysis for deutsche-biographie took 4.2417590618133545s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 5.602836608886719e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0005900859832763672s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.2762606143951416s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020470857620239258s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.435943603515625e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 6.869256496429443s
Availability | SPARQL endpoint availability check for dev8d took 4.2438507080078125e-05s
Availability | VoID file availability check for dev8d took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for dev8d took 0.28783273696899414s
Reputation | Calculation of the PageRank for dev8d took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for dev8d took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.771087646484375e-05s
Believability | Calculation of trust value for dev8d took 7.867813110351562e-06s
INFO | --- Analysis for dev8d took 3.101802110671997s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 30.094006061553955s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.26878976821899414s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.14984130859375e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.3909759521484375e-06s
INFO | --- Analysis for dewey_decimal_classification took 92.5215699672699s
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.0006487369537353516s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.26902008056640625s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 2.9325485229492188e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 5.7220458984375e-06s
INFO | --- Analysis for DHSVM took 15.42973518371582s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.1484832763671875e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2789299488067627s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 2.8848648071289062e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 6.9141387939453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.9886465072631836s
Availability | SPARQL endpoint availability check for Diavgeia took 4.5299530029296875e-05s
Availability | VoID file availability check for Diavgeia took 0.000598907470703125s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.2495121955871582s
Reputation | Calculation of the PageRank for Diavgeia took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.630752563476562e-05s
Believability | Calculation of trust value for Diavgeia took 5.245208740234375e-06s
INFO | --- Analysis for diavgeia took 5.69281792640686s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.3392181396484375e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0005617141723632812s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.27216339111328125s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011658668518066406s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for didactalia took 15.616882562637329s
Availability | SPARQL endpoint availability check for diigo.feed took 4.267692565917969e-05s
Availability | VoID file availability check for diigo.feed took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.278430700302124s
Reputation | Calculation of the PageRank for diigo.feed took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for diigo.feed took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.0040740966796875e-05s
Believability | Calculation of trust value for diigo.feed took 6.9141387939453125e-06s
INFO | --- Analysis for diigo-feed took 2.915520668029785s
Availability | SPARQL endpoint availability check for DisGeNET took 0.8517448902130127s
Availability | VoID file availability check for DisGeNET took 0.0006124973297119141s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2536966800689697s
Reputation | Calculation of the PageRank for DisGeNET took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001494884490966797s
Believability | Calculation of trust value for DisGeNET took 6.9141387939453125e-06s
INFO | --- Analysis for disgenet took 8.87558102607727s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.291534423828125e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.285991907119751s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020751953125s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.337860107421875e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 6.4373016357421875e-06s
INFO | --- Analysis for disk took 2.9850494861602783s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 5.316734313964844e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.2924075126647949s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.24249267578125e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 7.867813110351562e-06s
INFO | --- Analysis for distritos-zaragoza took 2.9543988704681396s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 4.267692565917969e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0007369518280029297s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.262770414352417s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.719329833984375e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 7.3909759521484375e-06s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 7.40038800239563s
Availability | SPARQL endpoint availability check for DM2E took 4.267692565917969e-05s
Availability | VoID file availability check for DM2E took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for DM2E took 0.28955531120300293s
Reputation | Calculation of the PageRank for DM2E took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00011205673217773438s
Believability | Calculation of trust value for DM2E took 1.3113021850585938e-05s
INFO | --- Analysis for dm2e took 3.2082626819610596s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.482269287109375e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.3014860153198242s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.147125244140625e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.152557373046875e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.957547426223755s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 1.5899901390075684s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.3242671489715576s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.000152587890625s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 6.198883056640625e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 10.581051588058472s
Availability | SPARQL endpoint availability check for DOAP Store took 4.1961669921875e-05s
Availability | VoID file availability check for DOAP Store took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.27024102210998535s
Reputation | Calculation of the PageRank for DOAP Store took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.266334533691406e-05s
Believability | Calculation of trust value for DOAP Store took 7.62939453125e-06s
INFO | --- Analysis for doap_store took 2.9487147331237793s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 6.985664367675781e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0007233619689941406s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2574167251586914s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.021677255630493164s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007894039154052734s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.413459777832031e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 5.245208740234375e-06s
INFO | --- Analysis for doi took 7.970015048980713s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.696846008300781e-05s
Availability | VoID file availability check for Driggu Florentino took 0.00042319297790527344s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.29253292083740234s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020302772521972656s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.147125244140625e-05s
Believability | Calculation of trust value for Driggu Florentino took 7.3909759521484375e-06s
INFO | --- Analysis for Driggu took 3.202069044113159s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 7.062315940856934s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.25970959663391113s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.5762786865234375e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 6.67572021484375e-06s
INFO | --- Analysis for drug-data-hifm took 37.399826765060425s
Availability | SPARQL endpoint availability check for dspace took 4.076957702636719e-05s
Availability | VoID file availability check for dspace took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for dspace took 0.26970672607421875s
Reputation | Calculation of the PageRank for dspace took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for dspace took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for dspace took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for dspace took 3.0279159545898438e-05s
Believability | Calculation of trust value for dspace took 6.67572021484375e-06s
INFO | --- Analysis for dspace took 2.903150796890259s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 6.699562072753906e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.27951717376708984s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.123283386230469e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 8.106231689453125e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.9452502727508545s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 272.0127649307251s
Availability | VoID file availability check for MetaLex Document Server took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.2588319778442383s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.933906555175781e-05s
Believability | Calculation of trust value for MetaLex Document Server took 7.3909759521484375e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 555.3906316757202s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 1.9317691326141357s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.7019565105438232s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.02071690559387207s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 4.38690185546875e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 7.152557373046875e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 11.102189540863037s
Availability | SPARQL endpoint availability check for DWS-Group took 4.3392181396484375e-05s
Availability | VoID file availability check for DWS-Group took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.7210254669189453s
Reputation | Calculation of the PageRank for DWS-Group took 0.020589351654052734s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010228157043457031s
Believability | Calculation of trust value for DWS-Group took 1.1205673217773438e-05s
INFO | --- Analysis for dws-group took 3.937716484069824s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.363059997558594e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005755424499511719s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.8184108734130859s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.020531892776489258s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 2.9325485229492188e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 6.67572021484375e-06s
INFO | --- Analysis for E1 took 6.012181282043457s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 0.08828020095825195s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.25116491317749023s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.021240234375s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0012230873107910156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.0001761913299560547s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-alaska took 2.9793505668640137s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 0.06113386154174805s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.274200439453125s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.02078843116760254s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 6.914138793945312e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-cau took 2.519092559814453s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 0.04719090461730957s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.2610962390899658s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.5051379203796387s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 0.034345388412475586s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.00045180320739746094s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.2677428722381592s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.512901306152344e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-cdrewu took 2.5502641201019287s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 0.05293893814086914s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.00021314620971679688s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.27624011039733887s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020277738571166992s
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.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013566017150878906s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.0013580322265625e-05s
INFO | --- Analysis for eagle-i-dartmouth took 2.9729373455047607s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.04297757148742676s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2630579471588135s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 9.250640869140625e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-famu took 2.6029233932495117s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 0.04521799087524414s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.26918792724609375s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020638704299926758s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.00013494491577148438s
Believability | Calculation of trust value for eagle-i @ Harvard University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-harvard took 2.5134096145629883s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 0.030748367309570312s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.27753496170043945s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.02107715606689453s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0010025501251220703s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001583099365234375s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-hawaii took 2.4079296588897705s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 0.041129112243652344s
Availability | VoID file availability check for eagle-i @ Howard University took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.28431105613708496s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02081775665283203s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007913112640380859s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.794929504394531e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-howard took 2.580735921859741s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 0.03925442695617676s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.2791264057159424s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.5316340923309326s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 0.03145742416381836s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.2589712142944336s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00011515617370605469s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 6.4373016357421875e-06s
INFO | --- Analysis for eagle-i-jsu took 2.492504119873047s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 0.04061579704284668s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.0003390312194824219s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.2811319828033447s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.8623809814453125e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-meharry took 2.5291857719421387s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 0.04960799217224121s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.25226473808288574s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010371208190917969s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-montana took 2.4359397888183594s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 0.05207490921020508s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.25824928283691406s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.703636169433594e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 8.821487426757812e-06s
INFO | --- Analysis for eagle-i-msm took 2.5478734970092773s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 0.05420708656311035s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2760283946990967s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02084207534790039s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0008738040924072266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.00015234947204589844s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 8.58306884765625e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.52852725982666s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 0.04666852951049805s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0005648136138916016s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.2583000659942627s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007975101470947266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.771087646484375e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-psm took 2.471569299697876s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 0.037390708923339844s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.29056787490844727s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.0967254638671875e-05s
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.890296936035156e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-tsu took 2.4435248374938965s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.05942654609680176s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2549266815185547s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.0007970333099365234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 7.081031799316406e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.519030809402466s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 0.04335904121398926s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.2541499137878418s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 0.00010442733764648438s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-uccaribe took 2.539368152618408s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0729227066040039s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.2852189540863037s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02032160758972168s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012350082397460938s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-upr took 2.503133535385132s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 0.045248985290527344s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2556779384613037s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.020644664764404297s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.103515625e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-utep took 2.512749433517456s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 0.06851696968078613s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.2477707862854004s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02158665657043457s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0010399818420410156s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 8.559226989746094e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-utsa took 2.5086162090301514s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 0.174574613571167s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.254622220993042s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02112579345703125s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0008535385131835938s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00011348724365234375s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 2.664365291595459s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 0.04564166069030762s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.25684428215026855s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020806312561035156s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0010614395141601562s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 9.465217590332031e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-xula took 2.504159688949585s
Availability | SPARQL endpoint availability check for Emergency situation took 0.6412127017974854s
Availability | VoID file availability check for Emergency situation took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.2590620517730713s
Reputation | Calculation of the PageRank for Emergency situation took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.935264587402344e-05s
Believability | Calculation of trust value for Emergency situation took 7.152557373046875e-06s
INFO | --- Analysis for Earthquake took 3.798264503479004s
Availability | SPARQL endpoint availability check for ESO took 0.5664937496185303s
Availability | VoID file availability check for ESO took 0.0003879070281982422s
Completeness | Calculation of interlinking completeness for ESO took 0.29368042945861816s
Reputation | Calculation of the PageRank for ESO took 0.023852825164794922s
Interlinking | Calculation of Degree of Connection for ESO took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for ESO took 0.0012869834899902344s
Interlinking | Calculation of Clustering coefficient for ESO took 0.00011038780212402344s
Believability | Calculation of trust value for ESO took 9.059906005859375e-06s
INFO | --- Analysis for Earthquake_case took 4.193999528884888s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 0.42319583892822266s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.2410602569580078s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.022864103317260742s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0008366107940673828s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00011730194091796875s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for ecb-linked-data took 2.8275697231292725s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 4.716799020767212s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0007152557373046875s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.2521042823791504s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020554780960083008s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.267692565917969e-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 10.690505743026733s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 2.0046184062957764s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.30692601203918457s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0008339881896972656s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.104873657226562e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 6.682287216186523s
Availability | SPARQL endpoint availability check for ECLAP took 20.525396585464478s
Availability | VoID file availability check for ECLAP took 0.0003001689910888672s
Completeness | Calculation of interlinking completeness for ECLAP took 0.2599754333496094s
Reputation | Calculation of the PageRank for ECLAP took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.124641418457031e-05s
Believability | Calculation of trust value for ECLAP took 8.344650268554688e-06s
INFO | --- Analysis for eclap took 53.00784945487976s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 5.602836608886719e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0006911754608154297s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2713789939880371s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2874603271484375e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 7.867813110351562e-06s
INFO | --- Analysis for ECNU-GISer took 4.185470819473267s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 7.2479248046875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2711665630340576s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.626678466796875e-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 3.058274507522583s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.315376281738281e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0003688335418701172s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.2620735168457031s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.021324872970581055s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.266334533691406e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 8.344650268554688e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.899214506149292s
Availability | SPARQL endpoint availability check for Edublogs took 4.410743713378906e-05s
Availability | VoID file availability check for Edublogs took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Edublogs took 0.2755866050720215s
Reputation | Calculation of the PageRank for Edublogs took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.00010204315185546875s
Believability | Calculation of trust value for Edublogs took 7.3909759521484375e-06s
INFO | --- Analysis for edublogs took 3.379031181335449s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 0.4638683795928955s
Availability | VoID file availability check for education.data.gov.uk took 0.00031375885009765625s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.2797203063964844s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0010290145874023438s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 0.00010442733764648438s
Believability | Calculation of trust value for education.data.gov.uk took 8.58306884765625e-06s
INFO | --- Analysis for education-data-gov-uk took 4.434648513793945s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.100799560546875e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.2520430088043213s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020545005798339844s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.152557373046875e-06s
INFO | --- Analysis for education-openuplabs took 2.960789203643799s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 392.8154263496399s
Availability | VoID file availability check for Educational programs - SISVU took 0.0008785724639892578s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.840745210647583s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.02109551429748535s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.269050598144531e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.152557373046875e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1323.1201829910278s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 0.7630009651184082s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0006570816040039062s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2717459201812744s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.021160364151000977s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.172325134277344e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 5.245208740234375e-06s
INFO | --- Analysis for eea took 9.456249952316284s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 0.5267741680145264s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.6846129894256592s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.020503520965576172s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 7.62939453125e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 5.7220458984375e-06s
INFO | --- Analysis for eea-rod took 6.764283180236816s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 0.16449475288391113s
Availability | VoID file availability check for EEA Vocabularies took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.28967905044555664s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.020677804946899414s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.320808410644531e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.3909759521484375e-06s
INFO | --- Analysis for eea-vocabularies took 6.191286087036133s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.24681711196899414s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020673751831054688s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.170967102050781e-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 3.485133647918701s
Availability | SPARQL endpoint availability check for E-Government Ontology took 0.4546332359313965s
Availability | VoID file availability check for E-Government Ontology took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.28035569190979004s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.1948089599609375e-05s
Believability | Calculation of trust value for E-Government Ontology took 8.821487426757812e-06s
INFO | --- Analysis for EGovOntology took 4.400591850280762s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5372767448425293s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.000652313232421875s
Extra | Recovery of all triples for Aragon Interoperable Information Structure EI2A - aragon open data took 3.1345179080963135s
Performance | Total latancy measurement for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3160288333892822s
Amount of data | Number of triples check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6736040115356445s
Interoperability | New terms check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.0119528770446777s
Versatility | Languages check for Aragon Interoperable Information Structure EI2A - aragon open data took 60.32845330238342s
Interpretability | Number of blank nodes check for Aragon Interoperable Information Structure EI2A - aragon open data took 4.749855279922485s
Interpretability | RDF structures check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9795708656311035s
Versatility | Serialization formats check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2298202514648438s
Availability | RDF dump link check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2435007095336914s
License | MR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.6076064109802246s
License | HR license check for Aragon Interoperable Information Structure EI2A - aragon open data took 7.014008283615112s
Amount of data | Number of property check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2702624797821045s
Understandability | Number of label check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4992201328277588s
Understandability | URI regex check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.65606689453125s
Understandability | Vocabs check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3296678066253662s
Verifiability | Authors check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.4115736484527588s
Verifiability | Publishers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.25684642791748047s
Performance | Throughput check for Aragon Interoperable Information Structure EI2A - aragon open data took 10.99392557144165s
Amount of data | Check the number of entities for Aragon Interoperable Information Structure EI2A - aragon open data took 8.463859558105469e-05s
Verifiability | Contribs. check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.39899492263793945s
Interlinking | sameAs chians check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.29720568656921387s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.7605278491973877s
Interlinking | skos check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.24492216110229492s
Timeliness | dataset update frequency check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.9448041915893555s
Currency | Creation date check for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6941170692443848s
Currency | Modification date check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.571850061416626s
Rep.Conc. | URIs length for Aragon Interoperable Information Structure EI2A - aragon open data took 5.881489992141724s
Interoperability | New vocabularies check for Aragon Interoperable Information Structure EI2A - aragon open data took 2.1457672119140625e-06s
Consistency | Deprecated classes/propertiers check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.2347877025604248s
Accuracy | Check Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.36568665504455566s
Accuracy | Check Inverse Functional Property for Aragon Interoperable Information Structure EI2A - aragon open data took 0.337200403213501s
Accuracy | Check Empty annotation labels for Aragon Interoperable Information Structure EI2A - aragon open data took 1.2021255493164062s
Accuracy | Check White space in annotation for Aragon Interoperable Information Structure EI2A - aragon open data took 0.03015613555908203s
Accuracy | Check Datatype consistency for Aragon Interoperable Information Structure EI2A - aragon open data took 0.030443668365478516s
Consistency | Disjoint class check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.3900454044342041s
Consistency | Check Misplaced properties for Aragon Interoperable Information Structure EI2A - aragon open data took 4.437158823013306s
Consistency | Misplaced classes for Aragon Interoperable Information Structure EI2A - aragon open data took 0.632718563079834s
Consistency | Check Ontology hijacking for Aragon Interoperable Information Structure EI2A - aragon open data took 2.660430431365967s
Consistency | Check Invalid usage of undefined classes for Aragon Interoperable Information Structure EI2A - aragon open data took 1.3297901153564453s
Consistency | Check Invalid usage of undefined properties for Aragon Interoperable Information Structure EI2A - aragon open data took 5.258013010025024s
Conciseness | Check Extensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.036248207092285156s
Conciseness | Check Intensional conciseness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5020465850830078s
Security | Sign check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.5785126686096191s
Availability | Check URIs Dereferenciability for Aragon Interoperable Information Structure EI2A - aragon open data took 3227.509631872177s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 1.1676661968231201s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 5.364418029785156e-05s
Interoperability | Check the re-using of existing vocabs for Aragon Interoperable Information Structure EI2A - aragon open data took 1.6689300537109375e-06s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 6.9141387939453125e-06s
INFO | --- Analysis for ei2a took 12281.875498771667s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 5.221366882324219e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.2722477912902832s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010561943054199219s
Believability | Calculation of trust value for EIONET RDF Data took 4.76837158203125e-06s
INFO | --- Analysis for eionet-rdf took 5.212832450866699s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.38690185546875e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.7045893669128418s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 2.8133392333984375e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 6.198883056640625e-06s
INFO | --- Analysis for ElgooG_ took 3.6709401607513428s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 6.437301635742188e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2577965259552002s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.8133392333984375e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 7.867813110351562e-06s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 3.757378101348877s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 6.235776424407959s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.2904510498046875s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.02034735679626465s
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.0007824897766113281s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.62939453125e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.71661376953125e-05s
INFO | --- Analysis for elviajero took 21.94389533996582s
Availability | SPARQL endpoint availability check for EMN took 4.3392181396484375e-05s
Availability | VoID file availability check for EMN took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for EMN took 0.27878689765930176s
Reputation | Calculation of the PageRank for EMN took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for EMN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for EMN took 3.9577484130859375e-05s
Believability | Calculation of trust value for EMN took 7.3909759521484375e-06s
INFO | --- Analysis for emn took 3.5015110969543457s
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.0005424022674560547s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.26537394523620605s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020971059799194336s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.507469177246094e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 9.775161743164062e-06s
INFO | --- Analysis for enakting-co2emission took 2.8662610054016113s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.315376281738281e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.27129697799682617s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.1484832763671875e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 4.5299530029296875e-06s
INFO | --- Analysis for enakting-crime took 2.4011921882629395s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.24092984199523926s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 6.151199340820312e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for enakting-energy took 2.3938241004943848s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.601478576660156e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2801637649536133s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.560585021972656e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 5.0067901611328125e-06s
INFO | --- Analysis for enakting-mortality took 2.455270767211914s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.601478576660156e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.27476000785827637s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 3.4809112548828125e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 5.245208740234375e-06s
INFO | --- Analysis for enakting-nhs took 2.406273603439331s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 5.5789947509765625e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.2654109001159668s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020946979522705078s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 6.079673767089844e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for enakting-population took 2.429924964904785s
Availability | SPARQL endpoint availability check for Enel Shops took 4.124641418457031e-05s
Availability | VoID file availability check for Enel Shops took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.28206348419189453s
Reputation | Calculation of the PageRank for Enel Shops took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.337860107421875e-05s
Believability | Calculation of trust value for Enel Shops took 7.867813110351562e-06s
INFO | --- Analysis for enel-shops took 2.9561707973480225s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.076957702636719e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.28082871437072754s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 2.8848648071289062e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 7.62939453125e-06s
INFO | --- Analysis for energy-efficiency took 2.9090840816497803s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.2632918357849121s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.528594970703125e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.8593835830688477s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 4.315376281738281e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0006015300750732422s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2548186779022217s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.790855407714844e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.9321517944335938s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 6.580352783203125e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.252246618270874s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.020503759384155273s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.9087066650390625e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.9758663177490234s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 8.034706115722656e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.2555675506591797s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 2.9802322387695312e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.920254707336426s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.2622828483581543s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.00079345703125s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.9294931888580322s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.27411651611328125s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020540475845336914s
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.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.9836888313293457s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.2563474178314209s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 2.8848648071289062e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.902298927307129s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.7339744567871094s
Availability | VoID file availability check for English Heritage Periods List took 0.0008187294006347656s
Extra | Recovery of all triples for English Heritage Periods List took 0.43708181381225586s
Performance | Total latancy measurement for English Heritage Periods List took 2.0676186084747314s
Amount of data | Number of triples check for English Heritage Periods List took 0.561955451965332s
Versatility | Languages check for English Heritage Periods List took 0.3681621551513672s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5544507503509521s
Security | Check HTTPS for English Heritage Periods List took 0.2666659355163574s
Interpretability | RDF structures check for English Heritage Periods List took 0.3746664524078369s
Versatility | Serialization formats check for English Heritage Periods List took 1.609039068222046s
Availability | RDF dump link check for English Heritage Periods List took 0.4035334587097168s
License | MR license check for English Heritage Periods List took 0.5501217842102051s
License | HR license check for English Heritage Periods List took 0.48166441917419434s
Amount of data | Number of property check for English Heritage Periods List took 0.5274002552032471s
Understandability | Number of label check for English Heritage Periods List took 0.5979101657867432s
Understandability | URI regex check for English Heritage Periods List took 0.8374395370483398s
Understandability | Vocabs check for English Heritage Periods List took 0.5266554355621338s
Verifiability | Authors check for English Heritage Periods List took 0.6734194755554199s
Verifiability | Publishers check for English Heritage Periods List took 0.5377066135406494s
Performance | Throughput check for English Heritage Periods List took 13.286348104476929s
Amount of data | Check the number of entities for English Heritage Periods List took 7.200241088867188e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.4405858516693115s
Interlinking | sameAs chians check for English Heritage Periods List took 0.4530329704284668s
Interlinking | skos check for English Heritage Periods List took 0.4602534770965576s
Interlinking | skos check for English Heritage Periods List took 0.4100525379180908s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.49761486053466797s
Currency | Creation date check for English Heritage Periods List took 0.9409878253936768s
Currency | Modification date check for English Heritage Periods List took 0.9517378807067871s
Rep.Conc. | URIs length for English Heritage Periods List took 0.8044002056121826s
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.46182823181152344s
Accuracy | Check Functional Property for English Heritage Periods List took 0.41144609451293945s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.388932466506958s
Consistency | Disjoint class check for English Heritage Periods List took 0.4229245185852051s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3899531364440918s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.750739336013794s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014591217041015625s
Security | Sign check for English Heritage Periods List took 0.44174885749816895s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.27597570419311523s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.600120544433594e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.9073486328125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 8.106231689453125e-06s
INFO | --- Analysis for english-heritage-periods-list took 62.527756690979004s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 1.2243289947509766s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.5449552536010742s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2619292736053467s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020457744598388672s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.337860107421875e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 5.7220458984375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 7.980830907821655s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 0.752471923828125s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.5580780506134033s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.2698955535888672s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.337860107421875e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.7220458984375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 7.446401834487915s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.291534423828125e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.2438046932220459s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020525217056274414s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.1948089599609375e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 6.67572021484375e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.867687940597534s
Availability | SPARQL endpoint availability check for English WordNet took 4.38690185546875e-05s
Availability | VoID file availability check for English WordNet took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for English WordNet took 0.26807689666748047s
Reputation | Calculation of the PageRank for English WordNet took 0.0202484130859375s
Interlinking | Calculation of Degree of Connection for English WordNet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English WordNet took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.266334533691406e-05s
Believability | Calculation of trust value for English WordNet took 6.67572021484375e-06s
INFO | --- Analysis for english-wordnet took 2.9140305519104004s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.172325134277344e-05s
Availability | VoID file availability check for English Heritage Places took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.27094435691833496s
Reputation | Calculation of the PageRank for English Heritage Places took 0.0205690860748291s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 2.9802322387695312e-05s
Believability | Calculation of trust value for English Heritage Places took 6.67572021484375e-06s
INFO | --- Analysis for englishheritage_places took 2.7862329483032227s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 0.14362645149230957s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00021719932556152344s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.258023738861084s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.797645568847656e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 6.67572021484375e-06s
INFO | --- Analysis for enipedia took 2.5412778854370117s
Availability | SPARQL endpoint availability check for Enslaved.org took 5.1975250244140625e-05s
Availability | VoID file availability check for Enslaved.org took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2838594913482666s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.0994415283203125e-05s
Believability | Calculation of trust value for Enslaved.org took 5.9604644775390625e-06s
INFO | --- Analysis for enslaved.org took 4.726223468780518s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.10897326469421387s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.24627208709716797s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020586252212524414s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 5.602836608886719e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 6.67572021484375e-06s
INFO | --- Analysis for entice-graph took 2.3928205966949463s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.57763671875e-05s
Availability | VoID file availability check for Entrez Gene took 0.0007727146148681641s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.24781441688537598s
Reputation | Calculation of the PageRank for Entrez Gene took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.552436828613281e-05s
Believability | Calculation of trust value for Entrez Gene took 7.62939453125e-06s
INFO | --- Analysis for entrez_gene took 27.496219635009766s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.1484832763671875e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.27256035804748535s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.0279159545898438e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 7.3909759521484375e-06s
INFO | --- Analysis for entrez_gene_extract took 2.8665785789489746s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 1.0842084884643555s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0003581047058105469s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.24480962753295898s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0007233619689941406s
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 5.4836273193359375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 11.578833103179932s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.3296835422515869s
Availability | VoID file availability check for environment.data.gov.uk took 0.0006008148193359375s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.27131009101867676s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007576942443847656s
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 4.5299530029296875e-06s
INFO | --- Analysis for environment-data-gov-uk took 9.581406116485596s
Availability | SPARQL endpoint availability check for EARTh took 270.5607862472534s
Availability | VoID file availability check for EARTh took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for EARTh took 0.3562507629394531s
Reputation | Calculation of the PageRank for EARTh took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for EARTh took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for EARTh took 0.00010442733764648438s
Believability | Calculation of trust value for EARTh took 7.3909759521484375e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 562.0277318954468s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 0.6058669090270996s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00028514862060546875s
Extra | Recovery of all triples for Micka (EO metadata) @PSNC took 117.64754462242126s
Performance | Total latancy measurement for Micka (EO metadata) @PSNC took 0.948714017868042s
Amount of data | Number of triples check for Micka (EO metadata) @PSNC took 8.390709400177002s
Interoperability | New terms check for Micka (EO metadata) @PSNC took 16.26178479194641s
Versatility | Languages check for Micka (EO metadata) @PSNC took 300.17007517814636s
Interpretability | Number of blank nodes check for Micka (EO metadata) @PSNC took 3.121124029159546s
Interpretability | RDF structures check for Micka (EO metadata) @PSNC took 0.25071215629577637s
Versatility | Serialization formats check for Micka (EO metadata) @PSNC took 10.583640813827515s
Availability | RDF dump link check for Micka (EO metadata) @PSNC took 0.24991703033447266s
License | MR license check for Micka (EO metadata) @PSNC took 0.4826676845550537s
License | HR license check for Micka (EO metadata) @PSNC took 300.1486210823059s
Amount of data | Number of property check for Micka (EO metadata) @PSNC took 0.3161649703979492s
Understandability | Number of label check for Micka (EO metadata) @PSNC took 2.2848050594329834s
Understandability | URI regex check for Micka (EO metadata) @PSNC took 0.5987687110900879s
Understandability | Vocabs check for Micka (EO metadata) @PSNC took 0.31833600997924805s
Verifiability | Authors check for Micka (EO metadata) @PSNC took 0.2175612449645996s
Verifiability | Publishers check for Micka (EO metadata) @PSNC took 0.2643897533416748s
Performance | Throughput check for Micka (EO metadata) @PSNC took 11.269871950149536s
Amount of data | Check the number of entities for Micka (EO metadata) @PSNC took 7.939338684082031e-05s
Verifiability | Contribs. check for Micka (EO metadata) @PSNC took 0.19743800163269043s
Interlinking | sameAs chians check for Micka (EO metadata) @PSNC took 0.19420218467712402s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.532973051071167s
Interlinking | skos check for Micka (EO metadata) @PSNC took 0.44407033920288086s
Timeliness | dataset update frequency check for Micka (EO metadata) @PSNC took 5.499209403991699s
Currency | Creation date check for Micka (EO metadata) @PSNC took 0.47130441665649414s
Currency | Modification date check for Micka (EO metadata) @PSNC took 0.2198038101196289s
Rep.Conc. | URIs length for Micka (EO metadata) @PSNC took 152.7623381614685s
Interoperability | New vocabularies check for Micka (EO metadata) @PSNC took 7.867813110351562e-06s
Consistency | Deprecated classes/propertiers check for Micka (EO metadata) @PSNC took 0.1986854076385498s
Accuracy | Check Functional Property for Micka (EO metadata) @PSNC took 0.26513028144836426s
Accuracy | Check Inverse Functional Property for Micka (EO metadata) @PSNC took 0.26206326484680176s
Accuracy | Check Empty annotation labels for Micka (EO metadata) @PSNC took 47.49452614784241s
Accuracy | Check White space in annotation for Micka (EO metadata) @PSNC took 2.6661159992218018s
Accuracy | Check Datatype consistency for Micka (EO metadata) @PSNC took 2.6529648303985596s
Consistency | Disjoint class check for Micka (EO metadata) @PSNC took 0.20708465576171875s
Consistency | Check Misplaced properties for Micka (EO metadata) @PSNC took 85.51669406890869s
Consistency | Misplaced classes for Micka (EO metadata) @PSNC took 8.39519739151001s
Consistency | Check Ontology hijacking for Micka (EO metadata) @PSNC took 36.684438943862915s
Consistency | Check Invalid usage of undefined classes for Micka (EO metadata) @PSNC took 1.416924238204956s
Consistency | Check Invalid usage of undefined properties for Micka (EO metadata) @PSNC took 81.95134329795837s
Conciseness | Check Extensional conciseness for Micka (EO metadata) @PSNC took 2.731867551803589s
Conciseness | Check Intensional conciseness for Micka (EO metadata) @PSNC took 0.5568513870239258s
Security | Sign check for Micka (EO metadata) @PSNC took 0.6468064785003662s
Availability | Check URIs Dereferenciability for Micka (EO metadata) @PSNC took 10.133656978607178s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.5196783542633057s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.021120786666870117s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0008499622344970703s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 4.220008850097656e-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 8.106231689453125e-06s
INFO | --- Analysis for EO_metadata took 2271.7319629192352s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 4.9591064453125e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.750068187713623s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020813941955566406s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.5762786865234375e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 5.7220458984375e-06s
INFO | --- Analysis for EOKP-Datasets took 5.031712055206299s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.2438507080078125e-05s
Availability | VoID file availability check for EPA-CDR took 0.00067138671875s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.28178930282592773s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02064800262451172s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.409385681152344e-05s
Believability | Calculation of trust value for EPA-CDR took 5.9604644775390625e-06s
INFO | --- Analysis for epa-cdr took 8.799548864364624s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.124641418457031e-05s
Availability | VoID file availability check for EPA-FRS took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.29206228256225586s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.224082946777344e-05s
Believability | Calculation of trust value for EPA-FRS took 4.5299530029296875e-06s
INFO | --- Analysis for epa-frs took 10.692253589630127s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-RCRA took 0.0005753040313720703s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.26679563522338867s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020931482315063477s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.600120544433594e-05s
Believability | Calculation of trust value for EPA-RCRA took 8.821487426757812e-06s
INFO | --- Analysis for epa-rcra took 7.6354286670684814s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.315376281738281e-05s
Availability | VoID file availability check for EPA-SRS took 0.0006680488586425781s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.275681734085083s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.43865966796875e-05s
Believability | Calculation of trust value for EPA-SRS took 5.245208740234375e-06s
INFO | --- Analysis for epa-srs took 6.90773868560791s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.172325134277344e-05s
Availability | VoID file availability check for EPA-TRI took 0.0006177425384521484s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.26857519149780273s
Reputation | Calculation of the PageRank for EPA-TRI took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.4332275390625e-05s
Believability | Calculation of trust value for EPA-TRI took 8.344650268554688e-06s
INFO | --- Analysis for epa-tri took 5.890740394592285s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.1484832763671875e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.2732398509979248s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 7.414817810058594e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 6.4373016357421875e-06s
INFO | --- Analysis for epo took 2.9249157905578613s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 0.06609725952148438s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2625424861907959s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001270771026611328s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.518357753753662s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.5529484748840332s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.26256227493286133s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 7.939338684082031e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 5.4836273193359375e-06s
INFO | --- Analysis for eprtr took 4.109921455383301s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 0.9348165988922119s
Availability | VoID file availability check for Railway Infrastructure KG took 0.00035572052001953125s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.28185009956359863s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020416736602783203s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.0994415283203125e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 5.4836273193359375e-06s
INFO | --- Analysis for ERAKG took 3.346794843673706s
Availability | SPARQL endpoint availability check for reg took 4.363059997558594e-05s
Availability | VoID file availability check for reg took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for reg took 0.24867749214172363s
Reputation | Calculation of the PageRank for reg took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for reg took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for reg took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for reg took 1.239776611328125e-05s
Believability | Calculation of trust value for reg took 7.3909759521484375e-06s
INFO | --- Analysis for erg took 2.949272871017456s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.2701904773712158s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.27124691009521484s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.075599670410156e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 7.62939453125e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.9270682334899902s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.363059997558594e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0006816387176513672s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2783777713775635s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.845329284667969e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 5.0067901611328125e-06s
INFO | --- Analysis for esd-standards took 4.272996187210083s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.291534423828125e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.0006365776062011719s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.25888586044311523s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 9.393692016601562e-05s
Believability | Calculation of trust value for ESD-Toolkit took 8.106231689453125e-06s
INFO | --- Analysis for esd-toolkit took 3.204538583755493s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.363059997558594e-05s
Availability | VoID file availability check for Dataset Esis took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.27942800521850586s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020618200302124023s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 2.9802322387695312e-05s
Believability | Calculation of trust value for Dataset Esis took 6.198883056640625e-06s
INFO | --- Analysis for esislearning took 2.820338487625122s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.3392181396484375e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.27904725074768066s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.9802322387695312e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 5.245208740234375e-06s
INFO | --- Analysis for ESV took 3.2500481605529785s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 0.5113019943237305s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.2818784713745117s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020328044891357422s
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.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 5.9604644775390625e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 3.940748691558838s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 4.1441731452941895s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2548210620880127s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.510185241699219e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 5.7220458984375e-06s
INFO | --- Analysis for eu-agencies-bodies took 12.06983232498169s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 4.076957702636719e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.25638318061828613s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020715713500976562s
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.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.147125244140625e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 7.152557373046875e-06s
INFO | --- Analysis for eu-dgt-tm took 2.8486292362213135s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.2438507080078125e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.0007283687591552734s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2534360885620117s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020496129989624023s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.000759124755859375s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.414817810058594e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 5.4836273193359375e-06s
INFO | --- Analysis for eu-institutions took 5.70745849609375s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 0.8557634353637695s
Availability | VoID file availability check for EU Parliament Media Library took 0.0006129741668701172s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.25768375396728516s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.457069396972656e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 5.4836273193359375e-06s
INFO | --- Analysis for eu-parliament-media took 6.318579196929932s
Availability | SPARQL endpoint availability check for EU Who Is Who took 0.8021316528320312s
Availability | VoID file availability check for EU Who Is Who took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.27161669731140137s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.5762786865234375e-05s
Believability | Calculation of trust value for EU Who Is Who took 5.0067901611328125e-06s
INFO | --- Analysis for eu-who-is-who took 8.784065961837769s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 0.7281126976013184s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0005667209625244141s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2741508483886719s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020813703536987305s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.696846008300781e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for eumida-linked-data took 6.978923797607422s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.2828989028930664s
Availability | VoID file availability check for European Nature Information System took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.2607748508453369s
Reputation | Calculation of the PageRank for European Nature Information System took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00010561943054199219s
Believability | Calculation of trust value for European Nature Information System took 6.4373016357421875e-06s
INFO | --- Analysis for eunis took 6.113483428955078s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 3.906129837036133s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0006384849548339844s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.26650094985961914s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.104873657226562e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.1682510375976562e-05s
INFO | --- Analysis for eur-lex-rdf took 11.266010284423828s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 0.7037851810455322s
Availability | VoID file availability check for Standard Eurobarometer took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.27879786491394043s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.02048468589782715s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.291534423828125e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 5.9604644775390625e-06s
INFO | --- Analysis for eurobarometer-standard took 6.835643768310547s
Availability | SPARQL endpoint availability check for European Election Results took 0.7352354526519775s
Availability | VoID file availability check for European Election Results took 0.0007736682891845703s
Completeness | Calculation of interlinking completeness for European Election Results took 0.2994425296783447s
Reputation | Calculation of the PageRank for European Election Results took 0.020457029342651367s
Interlinking | Calculation of Degree of Connection for European Election Results took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Election Results took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.528594970703125e-05s
Believability | Calculation of trust value for European Election Results took 5.4836273193359375e-06s
INFO | --- Analysis for european-election-results took 7.544625759124756s
Availability | SPARQL endpoint availability check for EPO patents took 0.370959997177124s
Availability | VoID file availability check for EPO patents took 0.0004932880401611328s
Extra | Recovery of all triples for EPO patents took 52.2687885761261s
Performance | Total latancy measurement for EPO patents took 0.8206667900085449s
Amount of data | Number of triples check for EPO patents took 90.17271375656128s
Versatility | Languages check for EPO patents took 120.08384203910828s
Interpretability | Number of blank nodes check for EPO patents took 90.20674753189087s
Interpretability | RDF structures check for EPO patents took 0.2801809310913086s
Versatility | Serialization formats check for EPO patents took 0.30038952827453613s
Availability | RDF dump link check for EPO patents took 0.19829416275024414s
License | MR license check for EPO patents took 0.27947354316711426s
License | HR license check for EPO patents took 90.21373867988586s
Amount of data | Number of property check for EPO patents took 0.21283435821533203s
Understandability | Number of label check for EPO patents took 90.19569087028503s
Understandability | URI regex check for EPO patents took 0.6175107955932617s
Understandability | Vocabs check for EPO patents took 0.23286151885986328s
Verifiability | Authors check for EPO patents took 0.28548479080200195s
Verifiability | Publishers check for EPO patents took 0.22446918487548828s
Performance | Throughput check for EPO patents took 10.994991064071655s
Amount of data | Check the number of entities for EPO patents took 7.367134094238281e-05s
Verifiability | Contribs. check for EPO patents took 0.17928314208984375s
Interlinking | sameAs chians check for EPO patents took 0.21959209442138672s
Interlinking | skos check for EPO patents took 0.21760010719299316s
Interlinking | skos check for EPO patents took 0.23151803016662598s
Timeliness | dataset update frequency check for EPO patents took 0.1879253387451172s
Currency | Creation date check for EPO patents took 0.4542977809906006s
Currency | Modification date check for EPO patents took 0.38633012771606445s
Rep.Conc. | URIs length for EPO patents took 153.84303998947144s
Interoperability | New vocabularies check for EPO patents took 3.814697265625e-06s
Consistency | Deprecated classes/propertiers check for EPO patents took 0.1810007095336914s
Accuracy | Check Empty annotation labels for EPO patents took 19.98785161972046s
Accuracy | Check White space in annotation for EPO patents took 2.959656238555908s
Accuracy | Check Datatype consistency for EPO patents took 4.88520359992981s
Consistency | Disjoint class check for EPO patents took 0.21537518501281738s
Consistency | Check Misplaced properties for EPO patents took 120.28499221801758s
Consistency | Check Ontology hijacking for EPO patents took 21.635194063186646s
Consistency | Check Invalid usage of undefined classes for EPO patents took 1.6612482070922852s
Consistency | Check Invalid usage of undefined properties for EPO patents took 121.44966626167297s
Conciseness | Check Extensional conciseness for EPO patents took 2.8000688552856445s
Conciseness | Check Intensional conciseness for EPO patents took 0.34629130363464355s
Security | Sign check for EPO patents took 0.24184846878051758s
Availability | Check URIs Dereferenciability for EPO patents took 1.3074331283569336s
Completeness | Calculation of interlinking completeness for EPO patents took 1.244769811630249s
Reputation | Calculation of the PageRank for EPO patents took 0.02185225486755371s
Interlinking | Calculation of Degree of Connection for EPO patents took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for EPO patents took 0.0010747909545898438s
Interlinking | Calculation of Clustering coefficient for EPO patents took 6.771087646484375e-05s
Interoperability | Check the re-using of existing vocabs for EPO patents took 3.337860107421875e-06s
Believability | Calculation of trust value for EPO patents took 7.152557373046875e-06s
INFO | --- Analysis for European_Patent_Information took 1319.3656446933746s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 5.6743621826171875e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.7185585498809814s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 2.86102294921875e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for europeana-lod took 4.717279672622681s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 9.608268737792969e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.30910634994506836s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.020696401596069336s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.775161743164062e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 6.67572021484375e-06s
INFO | --- Analysis for europeana-lod-v1 took 8.61009430885315s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.02983999252319336s
Availability | VoID file availability check for Europeana SPARQL took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.2475283145904541s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.0067901611328125e-05s
Believability | Calculation of trust value for Europeana SPARQL took 7.152557373046875e-06s
INFO | --- Analysis for europeana-sparql took 4.238114595413208s
Availability | SPARQL endpoint availability check for EuroSentiment took 0.08130931854248047s
Availability | VoID file availability check for EuroSentiment took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.30455613136291504s
Reputation | Calculation of the PageRank for EuroSentiment took 0.02028036117553711s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.7670135498046875e-05s
Believability | Calculation of trust value for EuroSentiment took 9.5367431640625e-06s
INFO | --- Analysis for eurosentiment took 3.22381854057312s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 0.0005941390991210938s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.292586088180542s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.987022399902344e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 5.0067901611328125e-06s
INFO | --- Analysis for eurostat-rdf took 12.382707595825195s
Availability | SPARQL endpoint availability check for EuroVoc took 0.370572566986084s
Availability | VoID file availability check for EuroVoc took 0.0006279945373535156s
Extra | Recovery of all triples for EuroVoc took 93.5486536026001s
Performance | Total latancy measurement for EuroVoc took 0.6067664623260498s
Amount of data | Number of triples check for EuroVoc took 0.7875792980194092s
Interoperability | New terms check for EuroVoc took 12.60172724723816s
Versatility | Languages check for EuroVoc took 300.05586671829224s
Interpretability | Number of blank nodes check for EuroVoc took 5.094295263290405s
Security | Check HTTPS for EuroVoc took 0.3161649703979492s
Interpretability | RDF structures check for EuroVoc took 1.0623109340667725s
Versatility | Serialization formats check for EuroVoc took 5.492589950561523s
Availability | RDF dump link check for EuroVoc took 1.314194917678833s
License | MR license check for EuroVoc took 6.636313438415527s
License | HR license check for EuroVoc took 300.0865454673767s
Amount of data | Number of property check for EuroVoc took 0.38103508949279785s
Understandability | Number of label check for EuroVoc took 1.515409231185913s
Understandability | URI regex check for EuroVoc took 0.35535740852355957s
Understandability | Vocabs check for EuroVoc took 0.11365747451782227s
Verifiability | Authors check for EuroVoc took 0.10647153854370117s
Verifiability | Publishers check for EuroVoc took 0.26158809661865234s
Performance | Throughput check for EuroVoc took 10.616472482681274s
Amount of data | Check the number of entities for EuroVoc took 8.058547973632812e-05s
Verifiability | Contribs. check for EuroVoc took 0.23331904411315918s
Interlinking | sameAs chians check for EuroVoc took 1.197023630142212s
Interlinking | skos check for EuroVoc took 0.16286945343017578s
Interlinking | skos check for EuroVoc took 0.15895557403564453s
Timeliness | dataset update frequency check for EuroVoc took 0.24935364723205566s
Currency | Creation date check for EuroVoc took 0.6353695392608643s
Currency | Modification date check for EuroVoc took 0.16127848625183105s
Rep.Conc. | URIs length for EuroVoc took 113.35606598854065s
Interoperability | New vocabularies check for EuroVoc took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for EuroVoc took 0.14651203155517578s
Accuracy | Check Functional Property for EuroVoc took 0.18382644653320312s
Accuracy | Check Inverse Functional Property for EuroVoc took 0.14201903343200684s
Accuracy | Check Empty annotation labels for EuroVoc took 29.345593690872192s
Accuracy | Check White space in annotation for EuroVoc took 3.123375654220581s
Accuracy | Check Datatype consistency for EuroVoc took 2.600811004638672s
Consistency | Disjoint class check for EuroVoc took 0.18794512748718262s
Consistency | Check Misplaced properties for EuroVoc took 57.63935422897339s
Consistency | Misplaced classes for EuroVoc took 8.317837476730347s
Consistency | Check Ontology hijacking for EuroVoc took 35.221489906311035s
Consistency | Check Invalid usage of undefined classes for EuroVoc took 1.493473768234253s
Consistency | Check Invalid usage of undefined properties for EuroVoc took 56.59237599372864s
Conciseness | Check Extensional conciseness for EuroVoc took 3.0173473358154297s
Conciseness | Check Intensional conciseness for EuroVoc took 0.413226842880249s
Security | Sign check for EuroVoc took 0.11949324607849121s
Availability | Check URIs Dereferenciability for EuroVoc took 8.927565574645996s
Completeness | Calculation of interlinking completeness for EuroVoc took 1.9473187923431396s
Reputation | Calculation of the PageRank for EuroVoc took 0.021123647689819336s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.52587890625e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 8.96453857421875e-05s
Interoperability | Check the re-using of existing vocabs for EuroVoc took 1.6689300537109375e-06s
Believability | Calculation of trust value for EuroVoc took 6.67572021484375e-06s
INFO | --- Analysis for eurovoc took 14088.157159090042s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 4.673004150390625e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.6898391246795654s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 3.9577484130859375e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 7.867813110351562e-06s
INFO | --- Analysis for eurovoc-in-skos took 4.278595447540283s
Availability | SPARQL endpoint availability check for European Television Heritage took 4.38690185546875e-05s
Availability | VoID file availability check for European Television Heritage took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.2713582515716553s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020846128463745117s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0009899139404296875s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.2901763916015625e-05s
Believability | Calculation of trust value for European Television Heritage took 7.152557373046875e-06s
INFO | --- Analysis for euscreen took 3.4201574325561523s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.267692565917969e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2693290710449219s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.8160552978515625e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 4.76837158203125e-06s
INFO | --- Analysis for euskadi-farmacias took 5.50089693069458s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 0.7620151042938232s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.6860811710357666s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.0040740966796875e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 7.867813110351562e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 4.8614397048950195s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.26722121238708496s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.000942230224609375s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.2624671459197998s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.534027099609375e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 7.152557373046875e-06s
INFO | --- Analysis for eutc-productions took 6.889744758605957s
Availability | SPARQL endpoint availability check for EventMedia took 0.37004590034484863s
Availability | VoID file availability check for EventMedia took 0.0007126331329345703s
Completeness | Calculation of interlinking completeness for EventMedia took 0.25666308403015137s
Reputation | Calculation of the PageRank for EventMedia took 0.02083277702331543s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010633468627929688s
Believability | Calculation of trust value for EventMedia took 7.3909759521484375e-06s
INFO | --- Analysis for event-media took 10.024654626846313s
Availability | SPARQL endpoint availability check for EventKG took 5.435943603515625e-05s
Availability | VoID file availability check for EventKG took 0.0004105567932128906s
Completeness | Calculation of interlinking completeness for EventKG took 0.2732226848602295s
Reputation | Calculation of the PageRank for EventKG took 0.021210193634033203s
Interlinking | Calculation of Degree of Connection for EventKG took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.702278137207031e-05s
Believability | Calculation of trust value for EventKG took 7.867813110351562e-06s
INFO | --- Analysis for eventkg took 4.9315454959869385s
Availability | SPARQL endpoint availability check for Eventseer took 0.867011547088623s
Availability | VoID file availability check for Eventseer took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2648036479949951s
Reputation | Calculation of the PageRank for Eventseer took 0.020168781280517578s
Interlinking | Calculation of Degree of Connection for Eventseer took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eventseer took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.696846008300781e-05s
Believability | Calculation of trust value for Eventseer took 7.3909759521484375e-06s
INFO | --- Analysis for eventseer took 3.2280092239379883s
Availability | SPARQL endpoint availability check for Face Link took 7.104873657226562e-05s
Availability | VoID file availability check for Face Link took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Face Link took 0.257519006729126s
Reputation | Calculation of the PageRank for Face Link took 0.020714282989501953s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.409385681152344e-05s
Believability | Calculation of trust value for Face Link took 7.62939453125e-06s
INFO | --- Analysis for Face_Link took 2.3450698852539062s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.2438507080078125e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.2639334201812744s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0010101795196533203s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.910064697265625e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 7.62939453125e-06s
INFO | --- Analysis for facebook-lids took 2.9604129791259766s
Availability | SPARQL endpoint availability check for Fact Forge took 4.1961669921875e-05s
Availability | VoID file availability check for Fact Forge took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.27919626235961914s
Reputation | Calculation of the PageRank for Fact Forge took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.0517578125e-05s
Believability | Calculation of trust value for Fact Forge took 6.9141387939453125e-06s
INFO | --- Analysis for fact-forge took 2.8884198665618896s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5729894638061523s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.00026726722717285156s
Extra | Recovery of all triples for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 112.9060571193695s
Performance | Total latancy measurement for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.9967758655548096s
Amount of data | Number of triples check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.262994527816772s
Interoperability | New terms check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 13.058177471160889s
Versatility | Languages check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.18946981430054s
Interpretability | Number of blank nodes check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.291574478149414s
Interpretability | RDF structures check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.24033737182617188s
Versatility | Serialization formats check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 10.625985622406006s
Availability | RDF dump link check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21456360816955566s
License | MR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3681013584136963s
License | HR license check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 300.228152513504s
Amount of data | Number of property check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.3064730167388916s
Understandability | Number of label check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.4112114906311035s
Understandability | URI regex check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.6768176555633545s
Understandability | Vocabs check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.36259913444519043s
Verifiability | Authors check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.18724727630615234s
Verifiability | Publishers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.27097010612487793s
Performance | Throughput check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 11.339746236801147s
Amount of data | Check the number of entities for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.414817810058594e-05s
Verifiability | Contribs. check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19740581512451172s
Interlinking | sameAs chians check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.19738197326660156s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4453134536743164s
Interlinking | skos check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4282572269439697s
Timeliness | dataset update frequency check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.426609516143799s
Currency | Creation date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4739665985107422s
Currency | Modification date check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21874475479125977s
Rep.Conc. | URIs length for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 145.00772261619568s
Interoperability | New vocabularies check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.21718692779541016s
Accuracy | Check Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2560865879058838s
Accuracy | Check Inverse Functional Property for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.26119351387023926s
Accuracy | Check Empty annotation labels for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 40.63879108428955s
Accuracy | Check White space in annotation for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6741175651550293s
Accuracy | Check Datatype consistency for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.6104297637939453s
Consistency | Disjoint class check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.200117826461792s
Consistency | Check Misplaced properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 82.99053168296814s
Consistency | Misplaced classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.89073920249939s
Consistency | Check Ontology hijacking for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 37.966169118881226s
Consistency | Check Invalid usage of undefined classes for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.355422019958496s
Consistency | Check Invalid usage of undefined properties for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 83.07386612892151s
Conciseness | Check Extensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.752222776412964s
Conciseness | Check Intensional conciseness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.5435175895690918s
Security | Sign check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.4868006706237793s
Availability | Check URIs Dereferenciability for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.714487075805664s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.3465824127197266s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 5.91278076171875e-05s
Interoperability | Check the re-using of existing vocabs for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for FADN_(2019) took 2244.388802051544s
Availability | SPARQL endpoint availability check for FAMEData took 0.00010251998901367188s
Availability | VoID file availability check for FAMEData took 0.0006899833679199219s
Completeness | Calculation of interlinking completeness for FAMEData took 0.2631957530975342s
Reputation | Calculation of the PageRank for FAMEData took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.0040740966796875e-05s
Believability | Calculation of trust value for FAMEData took 6.4373016357421875e-06s
INFO | --- Analysis for famedata took 10.595378637313843s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 4.363059997558594e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0006856918334960938s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2600407600402832s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.870529174804688e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 5.4836273193359375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 8.760217666625977s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.1830005645751953s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.2642550468444824s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020411968231201172s
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.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010442733764648438s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for fao-linked-data took 3.1002416610717773s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 4.601478576660156e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.28373193740844727s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 2.956390380859375e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for FAO_species took 2.4089181423187256s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 20.76057243347168s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.2739694118499756s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 6.031990051269531e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 6.198883056640625e-06s
INFO | --- Analysis for farmbio-chembl took 65.5101010799408s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 4.267692565917969e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.2641472816467285s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 6.9141387939453125e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 3.377715587615967s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 5.340576171875e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.24782323837280273s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 7.152557373046875e-06s
INFO | --- Analysis for farolapp-dataset took 2.8534038066864014s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 5.4836273193359375e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.2696704864501953s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.02082347869873047s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007727146148681641s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 3.075599670410156e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 6.9141387939453125e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 3.3280842304229736s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.4345855712890625e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2755928039550781s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 2.9325485229492188e-05s
Believability | Calculation of trust value for I4.0-Onto took 7.867813110351562e-06s
INFO | --- Analysis for fatimazahra took 2.328953266143799s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.100799560546875e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.24527287483215332s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 2.86102294921875e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 7.867813110351562e-06s
INFO | --- Analysis for federal-economic-rdf took 2.859055280685425s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.124641418457031e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.2436521053314209s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020262718200683594s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 2.7894973754882812e-05s
Believability | Calculation of trust value for Feed Wrapper took 6.67572021484375e-06s
INFO | --- Analysis for feedwrapper-lids took 2.9342410564422607s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.315376281738281e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.2807188034057617s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.0517578125e-05s
Believability | Calculation of trust value for FHIR STU3 took 6.67572021484375e-06s
INFO | --- Analysis for FHIR_STU3 took 2.7497358322143555s
Availability | SPARQL endpoint availability check for FiESTA took 4.291534423828125e-05s
Availability | VoID file availability check for FiESTA took 0.000713348388671875s
Completeness | Calculation of interlinking completeness for FiESTA took 0.27741360664367676s
Reputation | Calculation of the PageRank for FiESTA took 0.020740985870361328s
Interlinking | Calculation of Degree of Connection for FiESTA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FiESTA took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.9577484130859375e-05s
Believability | Calculation of trust value for FiESTA took 8.106231689453125e-06s
INFO | --- Analysis for fiesta took 12.619546175003052s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.553794860839844e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.26892781257629395s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 2.9325485229492188e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.3909759521484375e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.3766000270843506s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.4345855712890625e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2924492359161377s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020507335662841797s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0009400844573974609s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 8.225440979003906e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 5.9604644775390625e-06s
INFO | --- Analysis for finnish-municipalities took 58.60278105735779s
Availability | SPARQL endpoint availability check for firmao took 4.1484832763671875e-05s
Availability | VoID file availability check for firmao took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for firmao took 0.26604557037353516s
Reputation | Calculation of the PageRank for firmao took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for firmao took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for firmao took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for firmao took 2.8848648071289062e-05s
Believability | Calculation of trust value for firmao took 7.62939453125e-06s
INFO | --- Analysis for firmao took 3.888073682785034s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.24915695190429688s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 2.6941299438476562e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.9114341735839844s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 0.19442415237426758s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0002663135528564453s
Extra | Recovery of all triples for Norway fishery stocks dataset @PSNC took 116.54824209213257s
Performance | Total latancy measurement for Norway fishery stocks dataset @PSNC took 0.9689426422119141s
Amount of data | Number of triples check for Norway fishery stocks dataset @PSNC took 8.15470814704895s
Interoperability | New terms check for Norway fishery stocks dataset @PSNC took 14.318726301193237s
Versatility | Languages check for Norway fishery stocks dataset @PSNC took 300.1600742340088s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset @PSNC took 3.403902292251587s
Interpretability | RDF structures check for Norway fishery stocks dataset @PSNC took 0.25354719161987305s
Versatility | Serialization formats check for Norway fishery stocks dataset @PSNC took 9.780365228652954s
Availability | RDF dump link check for Norway fishery stocks dataset @PSNC took 0.2514519691467285s
License | MR license check for Norway fishery stocks dataset @PSNC took 0.553016185760498s
License | HR license check for Norway fishery stocks dataset @PSNC took 300.2092914581299s
Amount of data | Number of property check for Norway fishery stocks dataset @PSNC took 0.21845388412475586s
Understandability | Number of label check for Norway fishery stocks dataset @PSNC took 2.40362286567688s
Understandability | URI regex check for Norway fishery stocks dataset @PSNC took 0.7703447341918945s
Understandability | Vocabs check for Norway fishery stocks dataset @PSNC took 0.4022071361541748s
Verifiability | Authors check for Norway fishery stocks dataset @PSNC took 0.21734952926635742s
Verifiability | Publishers check for Norway fishery stocks dataset @PSNC took 0.2579793930053711s
Performance | Throughput check for Norway fishery stocks dataset @PSNC took 11.261565208435059s
Amount of data | Check the number of entities for Norway fishery stocks dataset @PSNC took 7.05718994140625e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset @PSNC took 0.19938421249389648s
Interlinking | sameAs chians check for Norway fishery stocks dataset @PSNC took 0.1984567642211914s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.550445556640625s
Interlinking | skos check for Norway fishery stocks dataset @PSNC took 0.42960548400878906s
Timeliness | dataset update frequency check for Norway fishery stocks dataset @PSNC took 7.780971527099609s
Currency | Creation date check for Norway fishery stocks dataset @PSNC took 0.4799044132232666s
Currency | Modification date check for Norway fishery stocks dataset @PSNC took 0.2131037712097168s
Rep.Conc. | URIs length for Norway fishery stocks dataset @PSNC took 155.7247440814972s
Interoperability | New vocabularies check for Norway fishery stocks dataset @PSNC took 2.47955322265625e-05s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset @PSNC took 0.2116231918334961s
Accuracy | Check Functional Property for Norway fishery stocks dataset @PSNC took 0.30478501319885254s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset @PSNC took 0.26767921447753906s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset @PSNC took 41.72993445396423s
Accuracy | Check White space in annotation for Norway fishery stocks dataset @PSNC took 2.6653709411621094s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset @PSNC took 2.645515203475952s
Consistency | Disjoint class check for Norway fishery stocks dataset @PSNC took 0.19807910919189453s
Consistency | Check Misplaced properties for Norway fishery stocks dataset @PSNC took 81.47728371620178s
Consistency | Misplaced classes for Norway fishery stocks dataset @PSNC took 8.554810047149658s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset @PSNC took 37.24086809158325s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset @PSNC took 1.4295594692230225s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset @PSNC took 83.34449172019958s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset @PSNC took 2.7486395835876465s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset @PSNC took 0.6033618450164795s
Security | Sign check for Norway fishery stocks dataset @PSNC took 0.6324434280395508s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset @PSNC took 10.167270421981812s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 1.4750111103057861s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020911216735839844s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 4.887580871582031e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 2260.166567325592s
Availability | SPARQL endpoint availability check for Fishes of Texas took 5.91278076171875e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.2658853530883789s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.463859558105469e-05s
Believability | Calculation of trust value for Fishes of Texas took 7.3909759521484375e-06s
INFO | --- Analysis for fishes-of-texas took 3.35457181930542s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.649162292480469e-05s
Availability | VoID file availability check for flickr? wrappr took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.26734399795532227s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020776033401489258s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.34600830078125e-05s
Believability | Calculation of trust value for flickr? wrappr took 6.9141387939453125e-06s
INFO | --- Analysis for flickr-wrappr took 3.507619619369507s
Availability | SPARQL endpoint availability check for flickr.person took 3.981590270996094e-05s
Availability | VoID file availability check for flickr.person took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for flickr.person took 0.2908811569213867s
Reputation | Calculation of the PageRank for flickr.person took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.0279159545898438e-05s
Believability | Calculation of trust value for flickr.person took 7.62939453125e-06s
INFO | --- Analysis for flickr_person took 3.3582065105438232s
Availability | SPARQL endpoint availability check for flickr.videoobject took 3.9577484130859375e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.2656676769256592s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.02102804183959961s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.170967102050781e-05s
Believability | Calculation of trust value for flickr.videoobject took 6.67572021484375e-06s
INFO | --- Analysis for flickr_videoobject took 2.8172237873077393s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.76837158203125e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0005474090576171875s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.26638150215148926s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 2.9802322387695312e-05s
Believability | Calculation of trust value for Future land use simulation model took 7.3909759521484375e-06s
INFO | --- Analysis for FLUS took 7.5107927322387695s
Availability | SPARQL endpoint availability check for Fly-TED took 4.1961669921875e-05s
Availability | VoID file availability check for Fly-TED took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.2668135166168213s
Reputation | Calculation of the PageRank for Fly-TED took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Fly-TED took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.0279159545898438e-05s
Believability | Calculation of trust value for Fly-TED took 9.059906005859375e-06s
INFO | --- Analysis for fly-ted took 3.366241931915283s
Availability | SPARQL endpoint availability check for FlyAtlas took 5.626678466796875e-05s
Availability | VoID file availability check for FlyAtlas took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.25469541549682617s
Reputation | Calculation of the PageRank for FlyAtlas took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.147125244140625e-05s
Believability | Calculation of trust value for FlyAtlas took 7.62939453125e-06s
INFO | --- Analysis for flyatlas took 2.9090778827667236s
Availability | SPARQL endpoint availability check for Flybase took 1.9686551094055176s
Availability | VoID file availability check for Flybase took 0.0005440711975097656s
Completeness | Calculation of interlinking completeness for Flybase took 0.24843835830688477s
Reputation | Calculation of the PageRank for Flybase took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Flybase took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.4332275390625e-05s
Believability | Calculation of trust value for Flybase took 7.867813110351562e-06s
INFO | --- Analysis for flybase took 10.402508020401001s
Availability | SPARQL endpoint availability check for Flyted took 1.3493623733520508s
Availability | VoID file availability check for Flyted took 0.0005578994750976562s
Completeness | Calculation of interlinking completeness for Flyted took 0.25841307640075684s
Reputation | Calculation of the PageRank for Flyted took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for Flyted took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.0279159545898438e-05s
Believability | Calculation of trust value for Flyted took 6.9141387939453125e-06s
INFO | --- Analysis for flyted took 11.283233880996704s
Availability | SPARQL endpoint availability check for Foodista took 1.0928354263305664s
Availability | VoID file availability check for Foodista took 0.0006639957427978516s
Completeness | Calculation of interlinking completeness for Foodista took 0.25598621368408203s
Reputation | Calculation of the PageRank for Foodista took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for Foodista took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Foodista took 3.6716461181640625e-05s
Believability | Calculation of trust value for Foodista took 7.62939453125e-06s
INFO | --- Analysis for foodista took 11.173122882843018s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.18182921409606934s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2554619312286377s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.271766662597656e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.3909759521484375e-06s
INFO | --- Analysis for foodpedia took 2.5694291591644287s
Availability | SPARQL endpoint availability check for FORGE Course information took 6.4849853515625e-05s
Availability | VoID file availability check for FORGE Course information took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.25684571266174316s
Reputation | Calculation of the PageRank for FORGE Course information took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 2.765655517578125e-05s
Believability | Calculation of trust value for FORGE Course information took 8.106231689453125e-06s
INFO | --- Analysis for forge-course-information took 2.8541712760925293s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.315376281738281e-05s
Availability | VoID file availability check for FrameBase schema took 0.0003974437713623047s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2837646007537842s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02050042152404785s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0008914470672607422s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.9591064453125e-05s
Believability | Calculation of trust value for FrameBase schema took 7.867813110351562e-06s
INFO | --- Analysis for framebase-schema took 3.4146509170532227s
Availability | SPARQL endpoint availability check for FrameNet took 4.029273986816406e-05s
Availability | VoID file availability check for FrameNet took 0.0003287792205810547s
Completeness | Calculation of interlinking completeness for FrameNet took 0.24921131134033203s
Reputation | Calculation of the PageRank for FrameNet took 0.02046680450439453s
Interlinking | Calculation of Degree of Connection for FrameNet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FrameNet took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for FrameNet took 2.7894973754882812e-05s
Believability | Calculation of trust value for FrameNet took 7.62939453125e-06s
INFO | --- Analysis for framenet took 2.884920835494995s
Availability | SPARQL endpoint availability check for Framester took 0.00011873245239257812s
Availability | VoID file availability check for Framester took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Framester took 0.27072596549987793s
Reputation | Calculation of the PageRank for Framester took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for Framester took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Framester took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Framester took 7.200241088867188e-05s
Believability | Calculation of trust value for Framester took 6.198883056640625e-06s
INFO | --- Analysis for framester took 3.355189561843872s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 0.15041351318359375s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2565183639526367s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020304203033447266s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.463859558105469e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for frb-linked-data took 2.576814651489258s
Availability | SPARQL endpoint availability check for Freebase took 4.220008850097656e-05s
Availability | VoID file availability check for Freebase took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Freebase took 0.27556633949279785s
Reputation | Calculation of the PageRank for Freebase took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for Freebase took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Freebase took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00026607513427734375s
Believability | Calculation of trust value for Freebase took 5.9604644775390625e-06s
INFO | --- Analysis for freebase took 4.670040845870972s
Availability | SPARQL endpoint availability check for Freeyork took 4.5299530029296875e-05s
Availability | VoID file availability check for Freeyork took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Freeyork took 0.25188469886779785s
Reputation | Calculation of the PageRank for Freeyork took 0.02112746238708496s
Interlinking | Calculation of Degree of Connection for Freeyork took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Freeyork took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.000102996826171875s
Believability | Calculation of trust value for Freeyork took 6.4373016357421875e-06s
INFO | --- Analysis for freeyork-org took 2.9045841693878174s
Availability | SPARQL endpoint availability check for French School Program took 4.0531158447265625e-05s
Availability | VoID file availability check for French School Program took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for French School Program took 0.25753140449523926s
Reputation | Calculation of the PageRank for French School Program took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for French School Program took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for French School Program took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for French School Program took 2.86102294921875e-05s
Believability | Calculation of trust value for French School Program took 8.58306884765625e-06s
INFO | --- Analysis for french-school-program took 2.869671106338501s
Availability | SPARQL endpoint availability check for French School System took 4.744529724121094e-05s
Availability | VoID file availability check for French School System took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for French School System took 0.2442002296447754s
Reputation | Calculation of the PageRank for French School System took 0.020961284637451172s
Interlinking | Calculation of Degree of Connection for French School System took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for French School System took 0.000989675521850586s
Interlinking | Calculation of Clustering coefficient for French School System took 3.457069396972656e-05s
Believability | Calculation of trust value for French School System took 7.152557373046875e-06s
INFO | --- Analysis for french-school-system took 2.883246660232544s
Availability | SPARQL endpoint availability check for French TimeBank took 4.076957702636719e-05s
Availability | VoID file availability check for French TimeBank took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.27339625358581543s
Reputation | Calculation of the PageRank for French TimeBank took 0.020339488983154297s
Interlinking | Calculation of Degree of Connection for French TimeBank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 2.9325485229492188e-05s
Believability | Calculation of trust value for French TimeBank took 7.62939453125e-06s
INFO | --- Analysis for french-timebank took 2.975917100906372s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 0.7915194034576416s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0005431175231933594s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.2470567226409912s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.021219253540039062s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.001054525375366211s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 9.226799011230469e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-cordis took 4.492145776748657s
Availability | SPARQL endpoint availability check for DailyMed took 0.7502188682556152s
Availability | VoID file availability check for DailyMed took 0.0005915164947509766s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2689802646636963s
Reputation | Calculation of the PageRank for DailyMed took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for DailyMed took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DailyMed took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.322166442871094e-05s
Believability | Calculation of trust value for DailyMed took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-dailymed took 5.730881690979004s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.7673294544219971s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.2554011344909668s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.417533874511719e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-dblp took 4.425837993621826s
Availability | SPARQL endpoint availability check for Diseasome took 0.7401070594787598s
Availability | VoID file availability check for Diseasome took 0.0004057884216308594s
Completeness | Calculation of interlinking completeness for Diseasome took 0.25740551948547363s
Reputation | Calculation of the PageRank for Diseasome took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010848045349121094s
Believability | Calculation of trust value for Diseasome took 8.106231689453125e-06s
INFO | --- Analysis for fu-berlin-diseasome took 5.6129310131073s
Availability | SPARQL endpoint availability check for DrugBank took 0.7202699184417725s
Availability | VoID file availability check for DrugBank took 0.000606536865234375s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2651238441467285s
Reputation | Calculation of the PageRank for DrugBank took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.0001289844512939453s
Believability | Calculation of trust value for DrugBank took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-drugbank took 5.656979322433472s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 0.6963093280792236s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2829601764678955s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 3.123283386230469e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 4.468192100524902s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 0.7315268516540527s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.2886166572570801s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007865428924560547s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.677078247070312e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.7220458984375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 4.50185489654541s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 0.7069745063781738s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.26868700981140137s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.43865966796875e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-eures took 4.352618217468262s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.7430729866027832s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.291597843170166s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020209074020385742s
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.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.632110595703125e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 5.191557884216309s
Availability | SPARQL endpoint availability check for MediCare took 0.7183828353881836s
Availability | VoID file availability check for MediCare took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for MediCare took 0.2701725959777832s
Reputation | Calculation of the PageRank for MediCare took 0.020255088806152344s
Interlinking | Calculation of Degree of Connection for MediCare took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MediCare took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for MediCare took 3.933906555175781e-05s
Believability | Calculation of trust value for MediCare took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-medicare took 4.951227903366089s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 0.7009780406951904s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.0003266334533691406s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.24318432807922363s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.271766662597656e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 4.291944265365601s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 0.6899385452270508s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.00032639503479003906s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.2729971408843994s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.021088838577270508s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 9.989738464355469e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 7.867813110351562e-06s
INFO | --- Analysis for fu-berlin-sider took 4.900343656539917s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 0.7025322914123535s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2736845016479492s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 8.034706115722656e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 1.0728836059570312e-05s
INFO | --- Analysis for fu-berlin-stitch took 4.261924743652344s
Availability | SPARQL endpoint availability check for fvdb took 6.914138793945312e-05s
Availability | VoID file availability check for fvdb took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for fvdb took 0.28447985649108887s
Reputation | Calculation of the PageRank for fvdb took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for fvdb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for fvdb took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.0040740966796875e-05s
Believability | Calculation of trust value for fvdb took 7.152557373046875e-06s
INFO | --- Analysis for fv took 12.518479824066162s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.315376281738281e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.26898193359375s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.9087066650390625e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 7.62939453125e-06s
INFO | --- Analysis for GACS took 3.322693109512329s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.839897155761719e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.00034046173095703125s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.2821190357208252s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.8848648071289062e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 7.62939453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.904371738433838s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 5.221366882324219e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0006315708160400391s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.2943108081817627s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 3.981590270996094e-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.163260221481323s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 5.2928924560546875e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.2650113105773926s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.0207061767578125s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.989738464355469e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for garnicaplywood took 3.8628504276275635s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.839897155761719e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0006263256072998047s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.25737619400024414s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.02055668830871582s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.679794311523438e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.3909759521484375e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 7.3762757778167725s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 0.3662540912628174s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.2708120346069336s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020571231842041016s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 0.00011205673217773438s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for gemet took 5.370126724243164s
Availability | SPARQL endpoint availability check for gemet-annotated took 4.267692565917969e-05s
Availability | VoID file availability check for gemet-annotated took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.2699899673461914s
Reputation | Calculation of the PageRank for gemet-annotated took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for gemet-annotated took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.4809112548828125e-05s
Believability | Calculation of trust value for gemet-annotated took 6.9141387939453125e-06s
INFO | --- Analysis for gemet-annotated took 2.8884284496307373s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 0.7700917720794678s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0004229545593261719s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.25491905212402344s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.1484832763671875e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 6.67572021484375e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 4.100354909896851s
Availability | SPARQL endpoint availability check for Super Ontology took 0.7609238624572754s
Availability | VoID file availability check for Super Ontology took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2519855499267578s
Reputation | Calculation of the PageRank for Super Ontology took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Super Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 4.235142707824707s
Availability | SPARQL endpoint availability check for geo.place took 5.555152893066406e-05s
Availability | VoID file availability check for geo.place took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for geo.place took 0.2600681781768799s
Reputation | Calculation of the PageRank for geo.place took 0.021194934844970703s
Interlinking | Calculation of Degree of Connection for geo.place took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0008025169372558594s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.0279159545898438e-05s
Believability | Calculation of trust value for geo.place took 7.867813110351562e-06s
INFO | --- Analysis for geo_place took 2.780897617340088s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.696846008300781e-05s
Availability | VoID file availability check for Geographic detector model took 0.0006189346313476562s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.26775193214416504s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geographic detector model took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Geographic detector model took 7.152557373046875e-06s
INFO | --- Analysis for GeoDetector took 11.825186491012573s
Availability | SPARQL endpoint availability check for geodomainwn took 4.649162292480469e-05s
Availability | VoID file availability check for geodomainwn took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.25046229362487793s
Reputation | Calculation of the PageRank for geodomainwn took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.792213439941406e-05s
Believability | Calculation of trust value for geodomainwn took 6.9141387939453125e-06s
INFO | --- Analysis for geodomainwn took 6.630194187164307s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.220008850097656e-05s
Availability | VoID file availability check for GeoEcuador took 0.0006167888641357422s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2845139503479004s
Reputation | Calculation of the PageRank for GeoEcuador took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 2.5510787963867188e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.000812530517578125s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 9.799003601074219e-05s
Believability | Calculation of trust value for GeoEcuador took 7.62939453125e-06s
INFO | --- Analysis for geoecuador took 12.590180158615112s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.3731541633605957s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.2556464672088623s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.866455078125e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 7.3909759521484375e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 47.70073342323303s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2672085762023926s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.4332275390625e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.867813110351562e-06s
INFO | --- Analysis for geographic-openuplabs took 2.9897027015686035s
Availability | SPARQL endpoint availability check for GeoLinkedData took 0.448361873626709s
Availability | VoID file availability check for GeoLinkedData took 0.0005288124084472656s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.25846314430236816s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.021058320999145508s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0008096694946289062s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.0001125335693359375s
Believability | Calculation of trust value for GeoLinkedData took 9.298324584960938e-06s
INFO | --- Analysis for geolinkeddata took 3.8872902393341064s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.30192041397094727s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0010976791381835938s
Extra | Recovery of all triples for Geological Survey of Austria (GBA) - Thesaurus took 11.250293254852295s
Performance | Total latancy measurement for Geological Survey of Austria (GBA) - Thesaurus took 0.3757350444793701s
Amount of data | Number of triples check for Geological Survey of Austria (GBA) - Thesaurus took 0.1358644962310791s
Interoperability | New terms check for Geological Survey of Austria (GBA) - Thesaurus took 1.4246041774749756s
Versatility | Languages check for Geological Survey of Austria (GBA) - Thesaurus took 0.20428204536437988s
Interpretability | Number of blank nodes check for Geological Survey of Austria (GBA) - Thesaurus took 0.1540076732635498s
Security | Check HTTPS for Geological Survey of Austria (GBA) - Thesaurus took 0.18295598030090332s
Interpretability | RDF structures check for Geological Survey of Austria (GBA) - Thesaurus took 0.09385466575622559s
Versatility | Serialization formats check for Geological Survey of Austria (GBA) - Thesaurus took 0.08643460273742676s
Availability | RDF dump link check for Geological Survey of Austria (GBA) - Thesaurus took 0.06802153587341309s
License | MR license check for Geological Survey of Austria (GBA) - Thesaurus took 0.09275698661804199s
License | HR license check for Geological Survey of Austria (GBA) - Thesaurus took 1.9802320003509521s
Amount of data | Number of property check for Geological Survey of Austria (GBA) - Thesaurus took 0.09342098236083984s
Understandability | Number of label check for Geological Survey of Austria (GBA) - Thesaurus took 0.09513044357299805s
Understandability | URI regex check for Geological Survey of Austria (GBA) - Thesaurus took 0.14444255828857422s
Understandability | Vocabs check for Geological Survey of Austria (GBA) - Thesaurus took 0.09241724014282227s
Verifiability | Authors check for Geological Survey of Austria (GBA) - Thesaurus took 0.0766744613647461s
Verifiability | Publishers check for Geological Survey of Austria (GBA) - Thesaurus took 0.08536601066589355s
Performance | Throughput check for Geological Survey of Austria (GBA) - Thesaurus took 10.27455997467041s
Amount of data | Check the number of entities for Geological Survey of Austria (GBA) - Thesaurus took 7.390975952148438e-05s
Verifiability | Contribs. check for Geological Survey of Austria (GBA) - Thesaurus took 0.0687255859375s
Interlinking | sameAs chians check for Geological Survey of Austria (GBA) - Thesaurus took 0.06263399124145508s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.09283852577209473s
Interlinking | skos check for Geological Survey of Austria (GBA) - Thesaurus took 0.07757925987243652s
Timeliness | dataset update frequency check for Geological Survey of Austria (GBA) - Thesaurus took 0.06968355178833008s
Currency | Creation date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1605830192565918s
Currency | Modification date check for Geological Survey of Austria (GBA) - Thesaurus took 0.1589374542236328s
Rep.Conc. | URIs length for Geological Survey of Austria (GBA) - Thesaurus took 1.5652906894683838s
Interoperability | New vocabularies check for Geological Survey of Austria (GBA) - Thesaurus took 2.7503209114074707s
Consistency | Deprecated classes/propertiers check for Geological Survey of Austria (GBA) - Thesaurus took 0.1004328727722168s
Accuracy | Check Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.07608819007873535s
Accuracy | Check Inverse Functional Property for Geological Survey of Austria (GBA) - Thesaurus took 0.06083345413208008s
Accuracy | Check Empty annotation labels for Geological Survey of Austria (GBA) - Thesaurus took 0.31227707862854004s
Accuracy | Check White space in annotation for Geological Survey of Austria (GBA) - Thesaurus took 0.0072214603424072266s
Accuracy | Check Datatype consistency for Geological Survey of Austria (GBA) - Thesaurus took 0.22601079940795898s
Consistency | Disjoint class check for Geological Survey of Austria (GBA) - Thesaurus took 0.062058448791503906s
Consistency | Check Misplaced properties for Geological Survey of Austria (GBA) - Thesaurus took 0.20167088508605957s
Consistency | Misplaced classes for Geological Survey of Austria (GBA) - Thesaurus took 0.5243520736694336s
Consistency | Check Ontology hijacking for Geological Survey of Austria (GBA) - Thesaurus took 3.208082675933838s
Consistency | Check Invalid usage of undefined classes for Geological Survey of Austria (GBA) - Thesaurus took 1.5146429538726807s
Consistency | Check Invalid usage of undefined properties for Geological Survey of Austria (GBA) - Thesaurus took 1.7053711414337158s
Conciseness | Check Extensional conciseness for Geological Survey of Austria (GBA) - Thesaurus took 0.18039345741271973s
Security | Sign check for Geological Survey of Austria (GBA) - Thesaurus took 0.07548928260803223s
Availability | Check URIs Dereferenciability for Geological Survey of Austria (GBA) - Thesaurus took 1.0808203220367432s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.27370643615722656s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.082389831542969e-05s
Interoperability | Check the re-using of existing vocabs for Geological Survey of Austria (GBA) - Thesaurus took 2.1060450077056885s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 58.83855962753296s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.410743713378906e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.2623269557952881s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004627704620361328s
Believability | Calculation of trust value for GeoNames Semantic Web took 5.9604644775390625e-06s
INFO | --- Analysis for geonames-semantic-web took 3.1092803478240967s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.9591064453125e-05s
Availability | VoID file availability check for Geospatial World  took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.2755768299102783s
Reputation | Calculation of the PageRank for Geospatial World  took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010323524475097656s
Believability | Calculation of trust value for Geospatial World  took 6.9141387939453125e-06s
INFO | --- Analysis for geospatialworld-net took 2.842066526412964s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 0.566748857498169s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.00031566619873046875s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.24783062934875488s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.02009105682373047s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013446807861328125s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 6.4373016357421875e-06s
INFO | --- Analysis for geospecies took 5.791354656219482s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.1961669921875e-05s
Availability | VoID file availability check for GeoWordNet took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2530486583709717s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.792213439941406e-05s
Believability | Calculation of trust value for GeoWordNet took 6.67572021484375e-06s
INFO | --- Analysis for geowordnet took 7.363315582275391s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 0.07504653930664062s
Availability | VoID file availability check for German labor law thesaurus took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.2490217685699463s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.020333290100097656s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.867813110351562e-05s
Believability | Calculation of trust value for German labor law thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.430365800857544s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.27903079986572266s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 5.9604644775390625e-06s
INFO | --- Analysis for germlex took 22.50579833984375s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.4291706085205078s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.24615883827209473s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.020092248916625977s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.726119995117188e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.821487426757812e-06s
INFO | --- Analysis for gesis-thesoz took 5.656471252441406s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.8137423992156982s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.00033402442932128906s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.26647186279296875s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.152557373046875e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for getty-aat took 16.473329067230225s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.0087416172027588s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.2760143280029297s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020113706588745117s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 4.863739013671875e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 6.67572021484375e-06s
INFO | --- Analysis for getty-tgn took 12.60542917251587s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 0.29105377197265625s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.26807332038879395s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 2.7418136596679688e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 6.198883056640625e-06s
INFO | --- Analysis for gipuzkoademografia took 2.815199613571167s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.482269287109375e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0007009506225585938s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.2745499610900879s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.020750999450683594s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0009274482727050781s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.647804260253906e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 7.3909759521484375e-06s
INFO | --- Analysis for glastonbury-2011 took 5.567434549331665s
Availability | SPARQL endpoint availability check for Global Change Information System took 4.267692565917969e-05s
Availability | VoID file availability check for Global Change Information System took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.296004056930542s
Reputation | Calculation of the PageRank for Global Change Information System took 0.02077317237854004s
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.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.0517578125e-05s
Believability | Calculation of trust value for Global Change Information System took 6.4373016357421875e-06s
INFO | --- Analysis for global-change-information-system took 2.865081310272217s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 4.291534423828125e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0007021427154541016s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.2918121814727783s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.021003246307373047s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.054473876953125e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 6.67572021484375e-06s
INFO | --- Analysis for global-hunger-index-2011 took 3.1523334980010986s
Availability | SPARQL endpoint availability check for Glottolog took 5.888938903808594e-05s
Availability | VoID file availability check for Glottolog took 0.0005726814270019531s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2741885185241699s
Reputation | Calculation of the PageRank for Glottolog took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for Glottolog took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Glottolog took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Glottolog took 5.125999450683594e-05s
Believability | Calculation of trust value for Glottolog took 7.62939453125e-06s
INFO | --- Analysis for glottolog took 6.352648019790649s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 7.271766662597656e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0007236003875732422s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.27074432373046875s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010061264038085938s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 8.58306884765625e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 10.17420220375061s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.220008850097656e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.25908780097961426s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.956390380859375e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 5.9604644775390625e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.915813446044922s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.1961669921875e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.26862502098083496s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.24249267578125e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.811981201171875e-05s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 3.0011136531829834s
Availability | SPARQL endpoint availability check for 1121 took 4.410743713378906e-05s
Availability | VoID file availability check for 1121 took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for 1121 took 0.2744309902191162s
Reputation | Calculation of the PageRank for 1121 took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for 1121 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.956390380859375e-05s
Believability | Calculation of trust value for 1121 took 6.67572021484375e-06s
INFO | --- Analysis for God_ took 3.3352067470550537s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 4.291534423828125e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.25879716873168945s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020700454711914062s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.1021575927734375e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 8.106231689453125e-06s
INFO | --- Analysis for gold took 4.070379257202148s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 7.581710815429688e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.0006060600280761719s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.307464599609375s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.02085280418395996s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 6.651878356933594e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 7.3909759521484375e-06s
INFO | --- Analysis for googleart-wrapper took 2.7145817279815674s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 0.09369564056396484s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2574882507324219s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020289897918701172s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.4332275390625e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 7.3909759521484375e-06s
INFO | --- Analysis for govagribus-denmark took 34.800045013427734s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 3.3925535678863525s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0007109642028808594s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.2732577323913574s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 9.036064147949219e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 5.7220458984375e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 31.2794291973114s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 1.6195356845855713s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0006246566772460938s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2473011016845703s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.678436279296875e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 5.245208740234375e-06s
INFO | --- Analysis for govtrack took 10.214755535125732s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.315376281738281e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0005779266357421875s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.23787546157836914s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 6.103515625e-05s
Believability | Calculation of trust value for greek-administrative-geography took 7.3909759521484375e-06s
INFO | --- Analysis for greek-administrative-geography took 2.5127902030944824s
Availability | SPARQL endpoint availability check for Greek Wordnet took 0.28569579124450684s
Availability | VoID file availability check for Greek Wordnet took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.26516294479370117s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020281553268432617s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 4.00543212890625e-05s
Believability | Calculation of trust value for Greek Wordnet took 7.867813110351562e-06s
INFO | --- Analysis for greek-wordnet took 2.754495859146118s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 2.913414239883423s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.28427767753601074s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.02039647102355957s
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.0007138252258300781s
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.3909759521484375e-06s
INFO | --- Analysis for greek_prisons_releases took 7.1885387897491455s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 0.9111378192901611s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.262876033782959s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.843971252441406e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.9141387939453125e-06s
INFO | --- Analysis for greekchildrensartmuseum took 4.5718584060668945s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 4.291534423828125e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0008885860443115234s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.26143789291381836s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.846687316894531e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 8.035159349441528s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 1.8523585796356201s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.3747103214263916s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.601478576660156e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 8.344650268554688e-06s
INFO | --- Analysis for grrp took 4.439184188842773s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 1.1099853515625s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.25747132301330566s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 7.081031799316406e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 5.4836273193359375e-06s
INFO | --- Analysis for grrt took 3.5242972373962402s
Availability | SPARQL endpoint availability check for Geological Timescale took 1.1287152767181396s
Availability | VoID file availability check for Geological Timescale took 0.0006253719329833984s
Extra | Recovery of all triples for Geological Timescale took 2.498800039291382s
Performance | Total latancy measurement for Geological Timescale took 3.579979658126831s
Amount of data | Number of triples check for Geological Timescale took 0.981560468673706s
Interoperability | New terms check for Geological Timescale took 1.7361924648284912s
Versatility | Languages check for Geological Timescale took 1.0533130168914795s
Interpretability | Number of blank nodes check for Geological Timescale took 0.43965625762939453s
Security | Check HTTPS for Geological Timescale took 0.37132740020751953s
Interpretability | RDF structures check for Geological Timescale took 0.3687930107116699s
Versatility | Serialization formats check for Geological Timescale took 0.3951375484466553s
Availability | RDF dump link check for Geological Timescale took 1.0275273323059082s
License | MR license check for Geological Timescale took 0.9543039798736572s
License | HR license check for Geological Timescale took 0.39937472343444824s
Amount of data | Number of property check for Geological Timescale took 0.3687007427215576s
Understandability | Number of label check for Geological Timescale took 0.9422602653503418s
Understandability | URI regex check for Geological Timescale took 1.83754301071167s
Understandability | Vocabs check for Geological Timescale took 0.9032299518585205s
Verifiability | Authors check for Geological Timescale took 0.9429454803466797s
Verifiability | Publishers check for Geological Timescale took 0.39676713943481445s
Performance | Throughput check for Geological Timescale took 14.04370403289795s
Amount of data | Check the number of entities for Geological Timescale took 0.019943952560424805s
Verifiability | Contribs. check for Geological Timescale took 0.40950989723205566s
Interlinking | sameAs chians check for Geological Timescale took 0.43624401092529297s
Interlinking | skos check for Geological Timescale took 0.3886067867279053s
Interlinking | skos check for Geological Timescale took 0.41283512115478516s
Timeliness | dataset update frequency check for Geological Timescale took 0.42045068740844727s
Currency | Creation date check for Geological Timescale took 1.3937363624572754s
Currency | Modification date check for Geological Timescale took 0.40186047554016113s
Rep.Conc. | URIs length for Geological Timescale took 1.5276257991790771s
Interoperability | New vocabularies check for Geological Timescale took 15.989408254623413s
Consistency | Deprecated classes/propertiers check for Geological Timescale took 0.8995769023895264s
Accuracy | Check Functional Property for Geological Timescale took 0.395233154296875s
Accuracy | Check Inverse Functional Property for Geological Timescale took 0.9086012840270996s
Accuracy | Check Empty annotation labels for Geological Timescale took 0.7769663333892822s
Accuracy | Check White space in annotation for Geological Timescale took 0.015395641326904297s
Accuracy | Check Datatype consistency for Geological Timescale took 0.07273006439208984s
Consistency | Disjoint class check for Geological Timescale took 0.38818907737731934s
Consistency | Check Misplaced properties for Geological Timescale took 1.3544042110443115s
Consistency | Misplaced classes for Geological Timescale took 1.037674903869629s
Consistency | Check Ontology hijacking for Geological Timescale took 1.7278385162353516s
Consistency | Check Invalid usage of undefined classes for Geological Timescale took 1.2929317951202393s
Consistency | Check Invalid usage of undefined properties for Geological Timescale took 2.272078275680542s
Conciseness | Check Extensional conciseness for Geological Timescale took 0.05040931701660156s
Conciseness | Check Intensional conciseness for Geological Timescale took 0.9745926856994629s
Security | Sign check for Geological Timescale took 0.9366590976715088s
Availability | Check URIs Dereferenciability for Geological Timescale took 2.726978063583374s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.2696530818939209s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 7.128715515136719e-05s
Interoperability | Check the re-using of existing vocabs for Geological Timescale took 15.221024513244629s
Believability | Calculation of trust value for Geological Timescale took 7.152557373046875e-06s
INFO | --- Analysis for GTS took 130.37616610527039s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.27448391914367676s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.314018249511719e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for GTS-ont took 2.6351230144500732s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.2438507080078125e-05s
Availability | VoID file availability check for GUTSTOK  took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.2590372562408447s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.9087066650390625e-05s
Believability | Calculation of trust value for GUTSTOK  took 6.4373016357421875e-06s
INFO | --- Analysis for Guillaume_Forget took 2.346836566925049s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.482269287109375e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.24997305870056152s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.866455078125e-05s
Believability | Calculation of trust value for Project Gutenberg took 6.67572021484375e-06s
INFO | --- Analysis for gutenberg took 8.690746068954468s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 5.53131103515625e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.0007672309875488281s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.2618567943572998s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.4332275390625e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 7.3909759521484375e-06s
INFO | --- Analysis for gwa-ili took 5.516164302825928s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.267692565917969e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0007338523864746094s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.26424360275268555s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.020296096801757812s
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.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 2.9802322387695312e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 7.62939453125e-06s
INFO | --- Analysis for GWR took 13.27142071723938s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.315376281738281e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0007033348083496094s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.24825382232666016s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 2.9087066650390625e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 7.867813110351562e-06s
INFO | --- Analysis for HASM took 9.123772144317627s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.2438507080078125e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.263336181640625s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007691383361816406s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 2.956390380859375e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.867813110351562e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.915860176086426s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 0.6088917255401611s
Availability | VoID file availability check for HealthCare Ontology took 0.0005500316619873047s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.2591409683227539s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.62396240234375e-05s
Believability | Calculation of trust value for HealthCare Ontology took 7.152557373046875e-06s
INFO | --- Analysis for HealthCare_Ontology took 3.572953939437866s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.38690185546875e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0005903244018554688s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.27486634254455566s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.021189451217651367s
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.0009219646453857422s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 7.224082946777344e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 7.3909759521484375e-06s
INFO | --- Analysis for heartfailure took 2.903376579284668s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.703808069229126s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0012128353118896484s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.2741386890411377s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020464420318603516s
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.0967254638671875e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.790855407714844e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 6.9141387939453125e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 121.20113921165466s
Availability | SPARQL endpoint availability check for Hedatuz took 0.3836057186126709s
Availability | VoID file availability check for Hedatuz took 0.0005159378051757812s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.24245572090148926s
Reputation | Calculation of the PageRank for Hedatuz took 0.02048802375793457s
Interlinking | Calculation of Degree of Connection for Hedatuz took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 3.743171691894531e-05s
Believability | Calculation of trust value for Hedatuz took 6.9141387939453125e-06s
INFO | --- Analysis for hedatuz took 3.086153268814087s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 0.12386131286621094s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2654762268066406s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.0001246929168701172s
Believability | Calculation of trust value for Hellenic Fire Brigade took 5.245208740234375e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.594757080078125s
Availability | SPARQL endpoint availability check for Hellenic Police took 0.023343801498413086s
Availability | VoID file availability check for Hellenic Police took 0.0006525516510009766s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.28228163719177246s
Reputation | Calculation of the PageRank for Hellenic Police took 0.021006107330322266s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0011341571807861328s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.0001552104949951172s
Believability | Calculation of trust value for Hellenic Police took 5.0067901611328125e-06s
INFO | --- Analysis for hellenic-police took 2.5879151821136475s
Availability | SPARQL endpoint availability check for Hermos took 4.410743713378906e-05s
Availability | VoID file availability check for Hermos took 0.0015914440155029297s
Completeness | Calculation of interlinking completeness for Hermos took 0.2393786907196045s
Reputation | Calculation of the PageRank for Hermos took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for Hermos took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hermos took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.956390380859375e-05s
Believability | Calculation of trust value for Hermos took 7.62939453125e-06s
INFO | --- Analysis for Hermos took 2.954836845397949s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.744529724121094e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2646613121032715s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.8133392333984375e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 7.152557373046875e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.3760695457458496s
Availability | SPARQL endpoint availability check for HITO took 0.4795074462890625s
Availability | VoID file availability check for HITO took 0.0005769729614257812s
Extra | Recovery of all triples for HITO took 3.2705225944519043s
Performance | Total latancy measurement for HITO took 0.9642186164855957s
Amount of data | Number of triples check for HITO took 0.19916605949401855s
Interoperability | New terms check for HITO took 1.4996442794799805s
Versatility | Languages check for HITO took 0.2085251808166504s
Interpretability | Number of blank nodes check for HITO took 0.19653797149658203s
Interpretability | RDF structures check for HITO took 0.19920897483825684s
Versatility | Serialization formats check for HITO took 0.19239020347595215s
Availability | RDF dump link check for HITO took 0.18691658973693848s
License | MR license check for HITO took 0.20004892349243164s
License | HR license check for HITO took 0.21170401573181152s
Amount of data | Number of property check for HITO took 0.19942736625671387s
Understandability | Number of label check for HITO took 0.19989657402038574s
Understandability | URI regex check for HITO took 0.3834364414215088s
Understandability | Vocabs check for HITO took 0.18585562705993652s
Verifiability | Authors check for HITO took 0.1883533000946045s
Verifiability | Publishers check for HITO took 0.1978011131286621s
Performance | Throughput check for HITO took 11.447335004806519s
Amount of data | Check the number of entities for HITO took 7.939338684082031e-05s
Verifiability | Contribs. check for HITO took 0.18584513664245605s
Interlinking | sameAs chians check for HITO took 0.19893646240234375s
Interlinking | skos check for HITO took 0.20924735069274902s
Interlinking | skos check for HITO took 0.1979689598083496s
Timeliness | dataset update frequency check for HITO took 0.20239877700805664s
Currency | Creation date check for HITO took 0.40699267387390137s
Currency | Modification date check for HITO took 0.4038543701171875s
Rep.Conc. | URIs length for HITO took 1.2115156650543213s
Interoperability | New vocabularies check for HITO took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for HITO took 0.18474650382995605s
Accuracy | Check Functional Property for HITO took 0.19783377647399902s
Accuracy | Check Inverse Functional Property for HITO took 0.20727086067199707s
Accuracy | Check Empty annotation labels for HITO took 0.5874946117401123s
Accuracy | Check White space in annotation for HITO took 0.013034582138061523s
Accuracy | Check Datatype consistency for HITO took 0.07038712501525879s
Consistency | Disjoint class check for HITO took 0.21135878562927246s
Consistency | Check Misplaced properties for HITO took 0.5366487503051758s
Consistency | Misplaced classes for HITO took 0.3750417232513428s
Consistency | Check Ontology hijacking for HITO took 1.7934436798095703s
Consistency | Check Invalid usage of undefined classes for HITO took 1.3020877838134766s
Consistency | Check Invalid usage of undefined properties for HITO took 1.568241834640503s
Conciseness | Check Extensional conciseness for HITO took 0.06045246124267578s
Conciseness | Check Intensional conciseness for HITO took 0.19443607330322266s
Security | Sign check for HITO took 0.20894575119018555s
Availability | Check URIs Dereferenciability for HITO took 2434.953771829605s
Completeness | Calculation of interlinking completeness for HITO took 1.617846965789795s
Reputation | Calculation of the PageRank for HITO took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for HITO took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for HITO took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for HITO took 9.441375732421875e-05s
Interoperability | Check the re-using of existing vocabs for HITO took 1.430511474609375e-06s
Believability | Calculation of trust value for HITO took 7.3909759521484375e-06s
INFO | --- Analysis for hito took 2490.8427612781525s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 6.9140784740448s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0006320476531982422s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.27836036682128906s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020261287689208984s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.147125244140625e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 7.62939453125e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 16.281110286712646s
Availability | SPARQL endpoint availability check for Homologene took 4.935264587402344e-05s
Availability | VoID file availability check for Homologene took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Homologene took 0.2608764171600342s
Reputation | Calculation of the PageRank for Homologene took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for Homologene took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Homologene took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.7179718017578125e-05s
Believability | Calculation of trust value for Homologene took 6.67572021484375e-06s
INFO | --- Analysis for homologene took 4.30447244644165s
Availability | SPARQL endpoint availability check for gseg took 4.267692565917969e-05s
Availability | VoID file availability check for gseg took 0.0006759166717529297s
Completeness | Calculation of interlinking completeness for gseg took 0.2795581817626953s
Reputation | Calculation of the PageRank for gseg took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for gseg took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for gseg took 2.8133392333984375e-05s
Believability | Calculation of trust value for gseg took 7.152557373046875e-06s
INFO | --- Analysis for hongse took 3.0964179039001465s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.076957702636719e-05s
Availability | VoID file availability check for Noticias Universia took 0.00022339820861816406s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.2658522129058838s
Reputation | Calculation of the PageRank for Noticias Universia took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 2.86102294921875e-05s
Believability | Calculation of trust value for Noticias Universia took 6.67572021484375e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 3.3350882530212402s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.076957702636719e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.2700176239013672s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.020426034927368164s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 2.7894973754882812e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 6.9141387939453125e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.971856117248535s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.5066494941711426s
Availability | VoID file availability check for COURAGE Dataset took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.27903127670288086s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for COURAGE Dataset took 5.9604644775390625e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 5.188076019287109s
Availability | SPARQL endpoint availability check for RoadTrb took 4.267692565917969e-05s
Availability | VoID file availability check for RoadTrb took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.28969264030456543s
Reputation | Calculation of the PageRank for RoadTrb took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for RoadTrb took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.86102294921875e-05s
Believability | Calculation of trust value for RoadTrb took 6.9141387939453125e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.409127950668335s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0006301403045654297s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.294830322265625s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020311594009399414s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.8371810913085938e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 26.09873604774475s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.220008850097656e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.2810368537902832s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.7418136596679688e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 6.9141387939453125e-06s
INFO | --- Analysis for http:pakistan.com took 2.294332265853882s
Availability | SPARQL endpoint availability check for CEDICT took 8.678436279296875e-05s
Availability | VoID file availability check for CEDICT took 0.0007982254028320312s
Completeness | Calculation of interlinking completeness for CEDICT took 0.260023832321167s
Reputation | Calculation of the PageRank for CEDICT took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for CEDICT took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CEDICT took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.457069396972656e-05s
Believability | Calculation of trust value for CEDICT took 1.239776611328125e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 4.348263740539551s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.5335619449615479s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2738926410675049s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.508827209472656e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.9141387939453125e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 4.712352752685547s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 5.412101745605469e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.25548410415649414s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.02068495750427246s
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.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.0279159545898438e-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.887829542160034s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.3392181396484375e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.27280592918395996s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 2.7418136596679688e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 6.67572021484375e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.3380746841430664s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.363059997558594e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.2687344551086426s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for Soccer Dataset took 7.867813110351562e-06s
INFO | --- Analysis for http:www.msm.com took 2.3224761486053467s
Availability | SPARQL endpoint availability check for Game Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Game Ontology took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.24037790298461914s
Reputation | Calculation of the PageRank for Game Ontology took 0.020090341567993164s
Interlinking | Calculation of Degree of Connection for Game Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.7179718017578125e-05s
Believability | Calculation of trust value for Game Ontology took 7.62939453125e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.8662054538726807s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.3392181396484375e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0006368160247802734s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2573366165161133s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.021271467208862305s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0010755062103271484s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.504753112792969e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.106231689453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 3.0530500411987305s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.2438507080078125e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.25947117805480957s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020395994186401367s
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.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.361219882965088s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.555152893066406e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2645108699798584s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9325485229492188e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.67572021484375e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.3123435974121094s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.363059997558594e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2534294128417969s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.7418136596679688e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.3589859008789062e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.399193525314331s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.3392181396484375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.27170896530151367s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02033829689025879s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8848648071289062e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.198883056640625e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.398153066635132s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.601478576660156e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0003502368927001953s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.24618077278137207s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9087066650390625e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.9141387939453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 3.636333465576172s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.5299530029296875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2686159610748291s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020213842391967773s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.86102294921875e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.67572021484375e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.3841567039489746s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.5299530029296875e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.25419187545776367s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020453691482543945s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.9087066650390625e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 6.67572021484375e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 4.049242258071899s
Availability | SPARQL endpoint availability check for Bookkeeping took 1.1188945770263672s
Availability | VoID file availability check for Bookkeeping took 0.0006573200225830078s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.26778745651245117s
Reputation | Calculation of the PageRank for Bookkeeping took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bookkeeping took 1.2636184692382812e-05s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 3.8974411487579346s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Legal Ontology took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.27428340911865234s
Reputation | Calculation of the PageRank for Legal Ontology took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for Legal Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.8865206241607666s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.291534423828125e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0005393028259277344s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.27385711669921875s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.2479248046875e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 7.867813110351562e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.7147576808929443s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.315376281738281e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0006434917449951172s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.2673356533050537s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007369518280029297s
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.527045488357544s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 4.029273986816406e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.2588214874267578s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020191192626953125s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 2.8371810913085938e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 6.4373016357421875e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 2.8523828983306885s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 9.512901306152344e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2688140869140625s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020256996154785156s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 2.8133392333984375e-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.897364377975464s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.2593746185302734s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.24014997482299805s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010323524475097656s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 7.62939453125e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 3.926987409591675s
Availability | SPARQL endpoint availability check for IATE RDF took 4.2438507080078125e-05s
Availability | VoID file availability check for IATE RDF took 0.0005478858947753906s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.2612571716308594s
Reputation | Calculation of the PageRank for IATE RDF took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for IATE RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IATE RDF took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.218650817871094e-05s
Believability | Calculation of trust value for IATE RDF took 1.1444091796875e-05s
INFO | --- Analysis for iate-rdf took 2.7375030517578125s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 6.110104084014893s
Availability | VoID file availability check for IATI as Linked Data took 0.0007483959197998047s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.24915599822998047s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.392333984375e-05s
Believability | Calculation of trust value for IATI as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for iati-as-linked-data took 13.11840534210205s
Availability | SPARQL endpoint availability check for ICANE took 0.4440584182739258s
Availability | VoID file availability check for ICANE took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for ICANE took 0.2663710117340088s
Reputation | Calculation of the PageRank for ICANE took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for ICANE took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICANE took 0.0007967948913574219s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.702278137207031e-05s
Believability | Calculation of trust value for ICANE took 5.4836273193359375e-06s
INFO | --- Analysis for icane took 3.7553675174713135s
Availability | SPARQL endpoint availability check for ichoose took 0.1525743007659912s
Availability | VoID file availability check for ichoose took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for ichoose took 0.24766874313354492s
Reputation | Calculation of the PageRank for ichoose took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for ichoose took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ichoose took 7.534027099609375e-05s
Believability | Calculation of trust value for ichoose took 7.62939453125e-06s
INFO | --- Analysis for ichoose took 47.79589343070984s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 0.586958646774292s
Availability | VoID file availability check for The Iconology Dataset took 0.0006716251373291016s
Extra | Recovery of all triples for The Iconology Dataset took 5.023346900939941s
Performance | Total latancy measurement for The Iconology Dataset took 0.481675386428833s
Amount of data | Number of triples check for The Iconology Dataset took 0.2187213897705078s
Interoperability | New terms check for The Iconology Dataset took 1.3969252109527588s
Versatility | Languages check for The Iconology Dataset took 0.5380909442901611s
Interpretability | Number of blank nodes check for The Iconology Dataset took 0.2059001922607422s
Interpretability | RDF structures check for The Iconology Dataset took 0.11539053916931152s
Versatility | Serialization formats check for The Iconology Dataset took 0.09598565101623535s
Availability | RDF dump link check for The Iconology Dataset took 0.0812375545501709s
License | MR license check for The Iconology Dataset took 0.09159016609191895s
License | HR license check for The Iconology Dataset took 0.2702357769012451s
Amount of data | Number of property check for The Iconology Dataset took 0.0973355770111084s
Understandability | Number of label check for The Iconology Dataset took 0.1479816436767578s
Understandability | URI regex check for The Iconology Dataset took 0.15991926193237305s
Understandability | Vocabs check for The Iconology Dataset took 0.08269214630126953s
Verifiability | Authors check for The Iconology Dataset took 0.1085970401763916s
Verifiability | Publishers check for The Iconology Dataset took 0.08600878715515137s
Performance | Throughput check for The Iconology Dataset took 10.43555212020874s
Amount of data | Check the number of entities for The Iconology Dataset took 0.0005211830139160156s
Verifiability | Contribs. check for The Iconology Dataset took 0.0862126350402832s
Interlinking | sameAs chians check for The Iconology Dataset took 0.079345703125s
Interlinking | skos check for The Iconology Dataset took 0.08878564834594727s
Interlinking | skos check for The Iconology Dataset took 0.08730053901672363s
Timeliness | dataset update frequency check for The Iconology Dataset took 0.08756875991821289s
Currency | Creation date check for The Iconology Dataset took 0.20174813270568848s
Currency | Modification date check for The Iconology Dataset took 0.1886143684387207s
Rep.Conc. | URIs length for The Iconology Dataset took 1.2960278987884521s
Interoperability | New vocabularies check for The Iconology Dataset took 6.198883056640625e-06s
Consistency | Deprecated classes/propertiers check for The Iconology Dataset took 0.08000802993774414s
Accuracy | Check Empty annotation labels for The Iconology Dataset took 0.2672278881072998s
Accuracy | Check White space in annotation for The Iconology Dataset took 0.016131877899169922s
Accuracy | Check Datatype consistency for The Iconology Dataset took 0.435138463973999s
Consistency | Disjoint class check for The Iconology Dataset took 0.08482241630554199s
Consistency | Check Misplaced properties for The Iconology Dataset took 0.1585700511932373s
Consistency | Misplaced classes for The Iconology Dataset took 0.8716058731079102s
Consistency | Check Ontology hijacking for The Iconology Dataset took 1.6865997314453125s
Consistency | Check Invalid usage of undefined classes for The Iconology Dataset took 1.2602062225341797s
Consistency | Check Invalid usage of undefined properties for The Iconology Dataset took 1.3308653831481934s
Conciseness | Check Extensional conciseness for The Iconology Dataset took 0.2904329299926758s
Security | Sign check for The Iconology Dataset took 0.08082842826843262s
Availability | Check URIs Dereferenciability for The Iconology Dataset took 2389.9427061080933s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 1.421565294265747s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.020588397979736328s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.8835067749023438e-05s
Interoperability | Check the re-using of existing vocabs for The Iconology Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The Iconology Dataset took 7.152557373046875e-06s
INFO | --- Analysis for iconology-dataset took 2449.143210887909s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.220008850097656e-05s
Availability | VoID file availability check for Identifiers.org took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.25241518020629883s
Reputation | Calculation of the PageRank for Identifiers.org took 0.02075648307800293s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 4.267692565917969e-05s
Believability | Calculation of trust value for Identifiers.org took 7.62939453125e-06s
INFO | --- Analysis for identifiers-org took 4.803694248199463s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 4.839897155761719e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2660942077636719s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 8.749961853027344e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 8.58306884765625e-06s
INFO | --- Analysis for idreffr took 4.303186655044556s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.6946828365325928s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.27098679542541504s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.982948303222656e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.71661376953125e-05s
INFO | --- Analysis for ids took 4.430533409118652s
Availability | SPARQL endpoint availability check for ietflang took 4.315376281738281e-05s
Availability | VoID file availability check for ietflang took 0.0007243156433105469s
Completeness | Calculation of interlinking completeness for ietflang took 0.26932644844055176s
Reputation | Calculation of the PageRank for ietflang took 0.020682334899902344s
Interlinking | Calculation of Degree of Connection for ietflang took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.5299530029296875e-05s
Believability | Calculation of trust value for ietflang took 6.198883056640625e-06s
INFO | --- Analysis for ietflang took 12.516146659851074s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 0.6608097553253174s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.2911393642425537s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.457069396972656e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for IGVLL took 4.280897617340088s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 0.5026130676269531s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.000545501708984375s
Extra | Recovery of all triples for 3LGM² IHE Ontology took 1.8230764865875244s
Performance | Total latancy measurement for 3LGM² IHE Ontology took 0.9677889347076416s
Amount of data | Number of triples check for 3LGM² IHE Ontology took 0.20699143409729004s
Interoperability | New terms check for 3LGM² IHE Ontology took 1.4856765270233154s
Versatility | Languages check for 3LGM² IHE Ontology took 0.21427130699157715s
Interpretability | Number of blank nodes check for 3LGM² IHE Ontology took 0.18508553504943848s
Interpretability | RDF structures check for 3LGM² IHE Ontology took 0.20859360694885254s
Versatility | Serialization formats check for 3LGM² IHE Ontology took 0.21093106269836426s
Availability | RDF dump link check for 3LGM² IHE Ontology took 0.19674921035766602s
License | MR license check for 3LGM² IHE Ontology took 0.20490765571594238s
License | HR license check for 3LGM² IHE Ontology took 0.20347094535827637s
Amount of data | Number of property check for 3LGM² IHE Ontology took 1.3808226585388184s
Understandability | Number of label check for 3LGM² IHE Ontology took 0.9948468208312988s
Understandability | URI regex check for 3LGM² IHE Ontology took 0.4085564613342285s
Understandability | Vocabs check for 3LGM² IHE Ontology took 0.19540643692016602s
Verifiability | Authors check for 3LGM² IHE Ontology took 0.20437407493591309s
Verifiability | Publishers check for 3LGM² IHE Ontology took 0.19651222229003906s
Performance | Throughput check for 3LGM² IHE Ontology took 11.416127920150757s
Amount of data | Check the number of entities for 3LGM² IHE Ontology took 7.605552673339844e-05s
Verifiability | Contribs. check for 3LGM² IHE Ontology took 0.20749902725219727s
Interlinking | sameAs chians check for 3LGM² IHE Ontology took 0.1969294548034668s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20695877075195312s
Interlinking | skos check for 3LGM² IHE Ontology took 0.20705318450927734s
Timeliness | dataset update frequency check for 3LGM² IHE Ontology took 0.19733357429504395s
Currency | Creation date check for 3LGM² IHE Ontology took 0.3816859722137451s
Currency | Modification date check for 3LGM² IHE Ontology took 0.3690524101257324s
Rep.Conc. | URIs length for 3LGM² IHE Ontology took 0.8393464088439941s
Interoperability | New vocabularies check for 3LGM² IHE Ontology took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for 3LGM² IHE Ontology took 0.19509267807006836s
Accuracy | Check Functional Property for 3LGM² IHE Ontology took 0.20668792724609375s
Accuracy | Check Inverse Functional Property for 3LGM² IHE Ontology took 0.2061469554901123s
Accuracy | Check Empty annotation labels for 3LGM² IHE Ontology took 0.3286123275756836s
Accuracy | Check White space in annotation for 3LGM² IHE Ontology took 0.0036382675170898438s
Accuracy | Check Datatype consistency for 3LGM² IHE Ontology took 0.0507349967956543s
Consistency | Disjoint class check for 3LGM² IHE Ontology took 0.20612311363220215s
Consistency | Check Misplaced properties for 3LGM² IHE Ontology took 0.46743178367614746s
Consistency | Misplaced classes for 3LGM² IHE Ontology took 0.2811398506164551s
Consistency | Check Ontology hijacking for 3LGM² IHE Ontology took 1.604250192642212s
Consistency | Check Invalid usage of undefined classes for 3LGM² IHE Ontology took 1.2718167304992676s
Consistency | Check Invalid usage of undefined properties for 3LGM² IHE Ontology took 1.5508699417114258s
Conciseness | Check Extensional conciseness for 3LGM² IHE Ontology took 0.030838489532470703s
Conciseness | Check Intensional conciseness for 3LGM² IHE Ontology took 0.18509626388549805s
Security | Sign check for 3LGM² IHE Ontology took 0.2099592685699463s
Availability | Check URIs Dereferenciability for 3LGM² IHE Ontology took 411.51161432266235s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.3760337829589844s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.023200511932373047s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for 3LGM² IHE Ontology took 1.430511474609375e-06s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 8.344650268554688e-06s
INFO | --- Analysis for IHE took 459.8240387439728s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.09244251251220703s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0006422996520996094s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.2501039505004883s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020582199096679688s
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.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.170967102050781e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 6.4373016357421875e-06s
INFO | --- Analysis for iislod-test took 2.8857829570770264s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.458427429199219e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.25380873680114746s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02035665512084961s
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.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 2.9325485229492188e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 6.9141387939453125e-06s
INFO | --- Analysis for ILUSOC took 12.974057912826538s
Availability | SPARQL endpoint availability check for im@sparql took 1.5762197971343994s
Availability | VoID file availability check for im@sparql took 0.0005958080291748047s
Completeness | Calculation of interlinking completeness for im@sparql took 0.2684330940246582s
Reputation | Calculation of the PageRank for im@sparql took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for im@sparql took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for im@sparql took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.86102294921875e-05s
Believability | Calculation of trust value for im@sparql took 7.152557373046875e-06s
INFO | --- Analysis for im@sparql took 5.41694188117981s
Availability | SPARQL endpoint availability check for imagery bailingniao took 4.291534423828125e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0006260871887207031s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.2670121192932129s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020440101623535156s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 2.956390380859375e-05s
Believability | Calculation of trust value for imagery bailingniao took 7.152557373046875e-06s
INFO | --- Analysis for imagery_bailingniao took 3.5192909240722656s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 1.1241919994354248s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0007123947143554688s
Extra | Recovery of all triples for Imagesnippets Image Descriptions took 25.975478887557983s
Performance | Total latancy measurement for Imagesnippets Image Descriptions took 3.394914388656616s
Amount of data | Number of triples check for Imagesnippets Image Descriptions took 9.530601263046265s
Interoperability | New terms check for Imagesnippets Image Descriptions took 3.4950854778289795s
Versatility | Languages check for Imagesnippets Image Descriptions took 10.666148900985718s
Interpretability | Number of blank nodes check for Imagesnippets Image Descriptions took 7.522472381591797s
Security | Check HTTPS for Imagesnippets Image Descriptions took 0.7104580402374268s
Interpretability | RDF structures check for Imagesnippets Image Descriptions took 0.7173628807067871s
Versatility | Serialization formats check for Imagesnippets Image Descriptions took 0.7024431228637695s
Availability | RDF dump link check for Imagesnippets Image Descriptions took 0.7253701686859131s
License | MR license check for Imagesnippets Image Descriptions took 0.7173457145690918s
License | HR license check for Imagesnippets Image Descriptions took 10.690767288208008s
Amount of data | Number of property check for Imagesnippets Image Descriptions took 0.7211930751800537s
Understandability | Number of label check for Imagesnippets Image Descriptions took 2.6714134216308594s
Understandability | URI regex check for Imagesnippets Image Descriptions took 1.432119369506836s
Understandability | Vocabs check for Imagesnippets Image Descriptions took 0.7133123874664307s
Verifiability | Authors check for Imagesnippets Image Descriptions took 0.7308065891265869s
Verifiability | Publishers check for Imagesnippets Image Descriptions took 0.6730260848999023s
Performance | Throughput check for Imagesnippets Image Descriptions took 13.560575246810913s
Amount of data | Check the number of entities for Imagesnippets Image Descriptions took 7.200241088867188e-05s
Verifiability | Contribs. check for Imagesnippets Image Descriptions took 0.6701936721801758s
Interlinking | sameAs chians check for Imagesnippets Image Descriptions took 0.6984660625457764s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6797196865081787s
Interlinking | skos check for Imagesnippets Image Descriptions took 0.6763994693756104s
Timeliness | dataset update frequency check for Imagesnippets Image Descriptions took 0.6864910125732422s
Currency | Creation date check for Imagesnippets Image Descriptions took 1.3938624858856201s
Currency | Modification date check for Imagesnippets Image Descriptions took 1.424994945526123s
Rep.Conc. | URIs length for Imagesnippets Image Descriptions took 26.339802742004395s
Interoperability | New vocabularies check for Imagesnippets Image Descriptions took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Imagesnippets Image Descriptions took 0.7223734855651855s
Accuracy | Check Functional Property for Imagesnippets Image Descriptions took 0.7137494087219238s
Accuracy | Check Inverse Functional Property for Imagesnippets Image Descriptions took 0.7290866374969482s
Consistency | Disjoint class check for Imagesnippets Image Descriptions took 0.7140641212463379s
Consistency | Check Misplaced properties for Imagesnippets Image Descriptions took 7.281765699386597s
Consistency | Check Ontology hijacking for Imagesnippets Image Descriptions took 16.93444538116455s
Consistency | Check Invalid usage of undefined properties for Imagesnippets Image Descriptions took 7.951413631439209s
Conciseness | Check Extensional conciseness for Imagesnippets Image Descriptions took 0.00017571449279785156s
Security | Sign check for Imagesnippets Image Descriptions took 0.7036731243133545s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.28989171981811523s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.1597309112548828s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.751319885253906e-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 253.89328622817993s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 0.19912934303283691s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.2937314510345459s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020709514617919922s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 0.00010013580322265625s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for imf-linked-data took 3.5478689670562744s
Availability | SPARQL endpoint availability check for IMGpedia took 4.029273986816406e-05s
Availability | VoID file availability check for IMGpedia took 0.0003139972686767578s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2844421863555908s
Reputation | Calculation of the PageRank for IMGpedia took 0.02064228057861328s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.147125244140625e-05s
Believability | Calculation of trust value for IMGpedia took 8.106231689453125e-06s
INFO | --- Analysis for imgpedia took 3.4726874828338623s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 4.100799560546875e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.2610175609588623s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.8133392333984375e-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.3380091190338135s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 7.009506225585938e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.2497544288635254s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.2159347534179688e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 7.152557373046875e-06s
INFO | --- Analysis for Imtiaz took 2.5886611938476562s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.410743713378906e-05s
Availability | VoID file availability check for Royalty Free Music took 0.0007674694061279297s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.29604148864746094s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.8848648071289062e-05s
Believability | Calculation of trust value for Royalty Free Music took 6.67572021484375e-06s
INFO | --- Analysis for inaudio.org took 4.117082357406616s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.315376281738281e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2755861282348633s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.8133392333984375e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 1.2159347534179688e-05s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.9453279972076416s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 5.078315734863281e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.2952115535736084s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.02102041244506836s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.24249267578125e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 8.106231689453125e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.9331631660461426s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 0.45582008361816406s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0006885528564453125s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.25293517112731934s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.886222839355469e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 3.767261028289795s
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.0003714561462402344s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2739081382751465s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 2.86102294921875e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 7.867813110351562e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 3.023392677307129s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 7.843971252441406e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0005962848663330078s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2658209800720215s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00010633468627929688s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.867813110351562e-06s
INFO | --- Analysis for ineverycrea took 21.74357533454895s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.458427429199219e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0007348060607910156s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.26317691802978516s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.179115295410156e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 1.2874603271484375e-05s
INFO | --- Analysis for ineverycrea-argentina took 9.20613718032837s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 0.04594898223876953s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0007760524749755859s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.2788548469543457s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.020540237426757812s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 6.985664367675781e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.152557373046875e-06s
INFO | --- Analysis for influence-tracker-dataset took 12.944047689437866s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.8160552978515625e-05s
Availability | VoID file availability check for INSEMTIVES took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.254488468170166s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.123283386230469e-05s
Believability | Calculation of trust value for INSEMTIVES took 8.58306884765625e-06s
INFO | --- Analysis for insemtives took 2.885134696960449s
Availability | SPARQL endpoint availability check for instagram.person took 4.124641418457031e-05s
Availability | VoID file availability check for instagram.person took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for instagram.person took 0.24927568435668945s
Reputation | Calculation of the PageRank for instagram.person took 0.020641088485717773s
Interlinking | Calculation of Degree of Connection for instagram.person took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for instagram.person took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for instagram.person took 3.0279159545898438e-05s
Believability | Calculation of trust value for instagram.person took 8.106231689453125e-06s
INFO | --- Analysis for instagram_person took 2.8533105850219727s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.291534423828125e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.26926374435424805s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 2.956390380859375e-05s
Believability | Calculation of trust value for instagram.videoobject took 1.3589859008789062e-05s
INFO | --- Analysis for instagram_videoobject took 2.9150454998016357s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 6.318092346191406e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.25385022163391113s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.021052122116088867s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.170967102050781e-05s
Believability | Calculation of trust value for Instance Hub Countries took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-countries took 2.9390838146209717s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.410743713378906e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00038313865661621094s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.24653124809265137s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.02043890953063965s
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.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8133392333984375e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.3650295734405518s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.7206878662109375e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.2928962707519531s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.2874603271484375e-05s
INFO | --- Analysis for instance-hub-organizations took 2.8873653411865234s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.506111145019531e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2799415588378906s
Reputation | Calculation of the PageRank for Instance Hub People took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 2.7418136596679688e-05s
Believability | Calculation of trust value for Instance Hub People took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-people took 2.924964427947998s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.27541136741638184s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 2.9087066650390625e-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.8060779571533203s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 5.626678466796875e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2691152095794678s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.021770238876342773s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.0994415283203125e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 8.344650268554688e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.9843852519989014s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.2438507080078125e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.27889537811279297s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020386695861816406s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.956892251968384s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 5.2928924560546875e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.27039456367492676s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 2.7418136596679688e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.833899974822998s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.25404906272888184s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.020526885986328125s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 8.344650268554688e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.8839268684387207s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.172325134277344e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.25452136993408203s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.170967102050781e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.896634817123413s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.100799560546875e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.29366159439086914s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 2.7894973754882812e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 7.3909759521484375e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.9289796352386475s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 5.3882598876953125e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.25748181343078613s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 2.7894973754882812e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 6.9141387939453125e-06s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.9228780269622803s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.27578306198120117s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.655952453613281e-05s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for interactivemaps-gnoss took 8.927952527999878s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 4.482269287109375e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.28243160247802734s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020666837692260742s
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.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.0994415283203125e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 7.62939453125e-06s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.8789167404174805s
Availability | SPARQL endpoint availability check for intervalue took 0.1499021053314209s
Availability | VoID file availability check for intervalue took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for intervalue took 0.24479913711547852s
Reputation | Calculation of the PageRank for intervalue took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for intervalue took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for intervalue took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for intervalue took 9.1552734375e-05s
Believability | Calculation of trust value for intervalue took 7.3909759521484375e-06s
INFO | --- Analysis for intervalue took 2.5257270336151123s
Availability | SPARQL endpoint availability check for Inztrow took 4.291534423828125e-05s
Availability | VoID file availability check for Inztrow took 0.0006473064422607422s
Completeness | Calculation of interlinking completeness for Inztrow took 0.27461791038513184s
Reputation | Calculation of the PageRank for Inztrow took 0.020174741744995117s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.9802322387695312e-05s
Believability | Calculation of trust value for Inztrow took 1.1682510375976562e-05s
INFO | --- Analysis for Inztrow took 3.4547677040100098s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0006091594696044922s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.2585487365722656s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0009629726409912109s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.337860107421875e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 7.152557373046875e-06s
INFO | --- Analysis for ipbes took 3.765613079071045s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.267692565917969e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0006456375122070312s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.28528690338134766s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.291534423828125e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 7.152557373046875e-06s
INFO | --- Analysis for iptc-newscodes took 3.5520412921905518s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 5.4836273193359375e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.27083802223205566s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020703554153442383s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 2.86102294921875e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0009808540344238281s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.337860107421875e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 7.3909759521484375e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.8848090171813965s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 2.304372787475586s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.2642545700073242s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.870529174804688e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.152557373046875e-06s
INFO | --- Analysis for iserve took 8.975595951080322s
Availability | SPARQL endpoint availability check for ISIC V4 took 22.173839569091797s
Availability | VoID file availability check for ISIC V4 took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.2683718204498291s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020888328552246094s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007853507995605469s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.838539123535156e-05s
Believability | Calculation of trust value for ISIC V4 took 9.5367431640625e-06s
INFO | --- Analysis for isic-v4 took 116.76196837425232s
Availability | SPARQL endpoint availability check for Isidore took 4.220008850097656e-05s
Availability | VoID file availability check for Isidore took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Isidore took 0.291611909866333s
Reputation | Calculation of the PageRank for Isidore took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Isidore took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Isidore took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Isidore took 2.8371810913085938e-05s
Believability | Calculation of trust value for Isidore took 7.62939453125e-06s
INFO | --- Analysis for isidore took 3.0172712802886963s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.506111145019531e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.000682830810546875s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.2545793056488037s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.021257877349853516s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 3.719329833984375e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0008974075317382812s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.963180541992188e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 5.4836273193359375e-06s
INFO | --- Analysis for isil-dbpedia took 4.342755079269409s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.172325134277344e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.24071264266967773s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.152557373046875e-06s
INFO | --- Analysis for iso-3166-2-data took 2.9212257862091064s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.38690185546875e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2544867992401123s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.02073216438293457s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.4809112548828125e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 6.4373016357421875e-06s
INFO | --- Analysis for iso-639-oasis took 2.8429484367370605s
Availability | SPARQL endpoint availability check for ISOcat took 4.3392181396484375e-05s
Availability | VoID file availability check for ISOcat took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for ISOcat took 0.31201910972595215s
Reputation | Calculation of the PageRank for ISOcat took 0.020667552947998047s
Interlinking | Calculation of Degree of Connection for ISOcat took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISOcat took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for ISOcat took 5.936622619628906e-05s
Believability | Calculation of trust value for ISOcat took 6.67572021484375e-06s
INFO | --- Analysis for isocat took 33.167219400405884s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.57763671875e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0005562305450439453s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.25257396697998047s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.4332275390625e-05s
Believability | Calculation of trust value for ISOcat-metadata took 7.152557373046875e-06s
INFO | --- Analysis for isocat-metadata took 4.799107074737549s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.1961669921875e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.26554346084594727s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.0994415283203125e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-ihi took 2.894756555557251s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2947542667388916s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00058746337890625s
Extra | Recovery of all triples for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.052878141403198s
Performance | Total latancy measurement for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.7889904975891113s
Amount of data | Number of triples check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.22376561164855957s
Interoperability | New terms check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 3.059154987335205s
Versatility | Languages check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 90.30198311805725s
Interpretability | Number of blank nodes check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.23197054862976074s
Security | Check HTTPS for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.1020359992980957s
Interpretability | RDF structures check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18994808197021484s
Versatility | Serialization formats check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17910408973693848s
Availability | RDF dump link check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16393733024597168s
License | MR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.21997737884521484s
License | HR license check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 91.03903651237488s
Amount of data | Number of property check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20266294479370117s
Understandability | Number of label check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1543030738830566s
Understandability | URI regex check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.42423224449157715s
Understandability | Vocabs check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.225189208984375s
Verifiability | Authors check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20242810249328613s
Verifiability | Publishers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17144227027893066s
Performance | Throughput check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.579799890518188s
Amount of data | Check the number of entities for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.152557373046875e-05s
Verifiability | Contribs. check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2237255573272705s
Interlinking | sameAs chians check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2933347225189209s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5785768032073975s
Interlinking | skos check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.5489401817321777s
Timeliness | dataset update frequency check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.20941901206970215s
Currency | Creation date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2816894054412842s
Currency | Modification date check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16264677047729492s
Rep.Conc. | URIs length for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 15.813292026519775s
Interoperability | New vocabularies check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.16179275512695312s
Accuracy | Check Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15471482276916504s
Accuracy | Check Inverse Functional Property for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15207719802856445s
Accuracy | Check Empty annotation labels for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.405193328857422s
Accuracy | Check White space in annotation for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.314255952835083s
Accuracy | Check Datatype consistency for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.2668795585632324s
Consistency | Disjoint class check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17989325523376465s
Consistency | Check Misplaced properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.790360450744629s
Consistency | Misplaced classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.9527194499969482s
Consistency | Check Ontology hijacking for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 5.034169912338257s
Consistency | Check Invalid usage of undefined classes for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.304213523864746s
Consistency | Check Invalid usage of undefined properties for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 10.991515874862671s
Conciseness | Check Extensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.28672122955322266s
Conciseness | Check Intensional conciseness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.15773510932922363s
Security | Sign check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.18928003311157227s
Availability | Check URIs Dereferenciability for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 8.932128190994263s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.8012471199035645s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.00010204315185546875s
Interoperability | Check the re-using of existing vocabs for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.6689300537109375e-06s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-place took 467.22078227996826s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.2438507080078125e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.697791576385498s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.02103590965270996s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0010113716125488281s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.719329833984375e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-rmn took 4.278472185134888s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.16591882705688477s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.0006558895111083984s
Extra | Recovery of all triples for ISPRA - The Italian Data Buoy Network (RON) took 9.451477527618408s
Performance | Total latancy measurement for ISPRA - The Italian Data Buoy Network (RON) took 0.7858977317810059s
Amount of data | Number of triples check for ISPRA - The Italian Data Buoy Network (RON) took 0.2184591293334961s
Interoperability | New terms check for ISPRA - The Italian Data Buoy Network (RON) took 3.112332344055176s
Versatility | Languages check for ISPRA - The Italian Data Buoy Network (RON) took 91.48934412002563s
Interpretability | Number of blank nodes check for ISPRA - The Italian Data Buoy Network (RON) took 0.20581340789794922s
Security | Check HTTPS for ISPRA - The Italian Data Buoy Network (RON) took 0.12538576126098633s
Interpretability | RDF structures check for ISPRA - The Italian Data Buoy Network (RON) took 0.19326233863830566s
Versatility | Serialization formats check for ISPRA - The Italian Data Buoy Network (RON) took 0.18496489524841309s
Availability | RDF dump link check for ISPRA - The Italian Data Buoy Network (RON) took 0.14851164817810059s
License | MR license check for ISPRA - The Italian Data Buoy Network (RON) took 0.258434534072876s
License | HR license check for ISPRA - The Italian Data Buoy Network (RON) took 92.13776421546936s
Amount of data | Number of property check for ISPRA - The Italian Data Buoy Network (RON) took 0.18825411796569824s
Understandability | Number of label check for ISPRA - The Italian Data Buoy Network (RON) took 1.2632012367248535s
Understandability | URI regex check for ISPRA - The Italian Data Buoy Network (RON) took 0.5059003829956055s
Understandability | Vocabs check for ISPRA - The Italian Data Buoy Network (RON) took 0.22077655792236328s
Verifiability | Authors check for ISPRA - The Italian Data Buoy Network (RON) took 0.19625163078308105s
Verifiability | Publishers check for ISPRA - The Italian Data Buoy Network (RON) took 0.14266490936279297s
Performance | Throughput check for ISPRA - The Italian Data Buoy Network (RON) took 10.734582901000977s
Amount of data | Check the number of entities for ISPRA - The Italian Data Buoy Network (RON) took 7.486343383789062e-05s
Verifiability | Contribs. check for ISPRA - The Italian Data Buoy Network (RON) took 0.2208385467529297s
Interlinking | sameAs chians check for ISPRA - The Italian Data Buoy Network (RON) took 0.2976350784301758s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.5923817157745361s
Interlinking | skos check for ISPRA - The Italian Data Buoy Network (RON) took 0.556875467300415s
Timeliness | dataset update frequency check for ISPRA - The Italian Data Buoy Network (RON) took 0.2291262149810791s
Currency | Creation date check for ISPRA - The Italian Data Buoy Network (RON) took 0.3317537307739258s
Currency | Modification date check for ISPRA - The Italian Data Buoy Network (RON) took 0.1401960849761963s
Rep.Conc. | URIs length for ISPRA - The Italian Data Buoy Network (RON) took 15.580156803131104s
Interoperability | New vocabularies check for ISPRA - The Italian Data Buoy Network (RON) took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for ISPRA - The Italian Data Buoy Network (RON) took 0.1562824249267578s
Accuracy | Check Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.16423869132995605s
Accuracy | Check Inverse Functional Property for ISPRA - The Italian Data Buoy Network (RON) took 0.15553760528564453s
Accuracy | Check Empty annotation labels for ISPRA - The Italian Data Buoy Network (RON) took 5.212580919265747s
Accuracy | Check White space in annotation for ISPRA - The Italian Data Buoy Network (RON) took 0.3096354007720947s
Accuracy | Check Datatype consistency for ISPRA - The Italian Data Buoy Network (RON) took 0.2614247798919678s
Consistency | Disjoint class check for ISPRA - The Italian Data Buoy Network (RON) took 0.13433527946472168s
Consistency | Check Misplaced properties for ISPRA - The Italian Data Buoy Network (RON) took 9.708122730255127s
Consistency | Misplaced classes for ISPRA - The Italian Data Buoy Network (RON) took 0.9520599842071533s
Consistency | Check Ontology hijacking for ISPRA - The Italian Data Buoy Network (RON) took 4.176220893859863s
Consistency | Check Invalid usage of undefined classes for ISPRA - The Italian Data Buoy Network (RON) took 1.2990808486938477s
Consistency | Check Invalid usage of undefined properties for ISPRA - The Italian Data Buoy Network (RON) took 10.883525371551514s
Conciseness | Check Extensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.2877204418182373s
Conciseness | Check Intensional conciseness for ISPRA - The Italian Data Buoy Network (RON) took 0.1796882152557373s
Security | Sign check for ISPRA - The Italian Data Buoy Network (RON) took 0.18605518341064453s
Availability | Check URIs Dereferenciability for ISPRA - The Italian Data Buoy Network (RON) took 8.997426271438599s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.4198482036590576s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020912885665893555s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 4.673004150390625e-05s
Interoperability | Check the re-using of existing vocabs for ISPRA - The Italian Data Buoy Network (RON) took 1.9073486328125e-06s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-ron took 463.2413070201874s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 4.172325134277344e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2677180767059326s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 6.198883056640625e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 7.867813110351562e-06s
INFO | --- Analysis for ispra-lod-sc took 3.753737688064575s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 0.7091622352600098s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0003848075866699219s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.25502681732177734s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 2.7179718017578125e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.00010442733764648438s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for issa-agritrop took 5.232668399810791s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.458427429199219e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.2522242069244385s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020467758178710938s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.9325485229492188e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.3909759521484375e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.730628728866577s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.38690185546875e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.000518798828125s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.26601433753967285s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.020568132400512695s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.170967102050781e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 5.4836273193359375e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 2.8859217166900635s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.506111145019531e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0005810260772705078s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.2698945999145508s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.147125244140625e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 1.239776611328125e-05s
INFO | --- Analysis for ISSN:_0080-3626. took 2.5363073348999023s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 1.6301531791687012s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0005862712860107422s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.27388954162597656s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 9.250640869140625e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 5.9604644775390625e-06s
INFO | --- Analysis for istat-immigration took 4.026212215423584s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.124641418457031e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.25095105171203613s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020638227462768555s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 3.0517578125e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.867813110351562e-06s
INFO | --- Analysis for istat-immigrazione took 2.8904781341552734s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 0.16403889656066895s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.2819359302520752s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.9087066650390625e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 5.7220458984375e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.835261583328247s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 1.1336913108825684s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.26680779457092285s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.534027099609375e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.3909759521484375e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 3.573990821838379s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.220008850097656e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0003256797790527344s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.2544565200805664s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007541179656982422s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 2.86102294921875e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 7.62939453125e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.8732945919036865s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.1484832763671875e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.27274107933044434s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.02051854133605957s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 2.8371810913085938e-05s
Believability | Calculation of trust value for IWMI Research Reports took 7.867813110351562e-06s
INFO | --- Analysis for iwmi-research-reports took 2.8336222171783447s
Availability | SPARQL endpoint availability check for IWN took 4.696846008300781e-05s
Availability | VoID file availability check for IWN took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for IWN took 0.27092671394348145s
Reputation | Calculation of the PageRank for IWN took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for IWN took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IWN took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for IWN took 3.933906555175781e-05s
Believability | Calculation of trust value for IWN took 7.152557373046875e-06s
INFO | --- Analysis for iwn took 5.789755582809448s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 4.172325134277344e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.2574961185455322s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02041769027709961s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 2.9802322387695312e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.62939453125e-06s
INFO | --- Analysis for j-global-knowledge took 2.865133285522461s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.220008850097656e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.2534968852996826s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020456552505493164s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.956390380859375e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 8.58306884765625e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.848464012145996s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 9.248462438583374s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2565948963165283s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 5.8650970458984375e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 6.9141387939453125e-06s
INFO | --- Analysis for jamendo-dbtune took 25.394590139389038s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 4.315376281738281e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.23658967018127441s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020293474197387695s
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.0008203983306884766s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.935264587402344e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.52587890625e-05s
INFO | --- Analysis for japan-radioactivity-stat took 4.296447515487671s
Availability | SPARQL endpoint availability check for JEL Classification took 4.8160552978515625e-05s
Availability | VoID file availability check for JEL Classification took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.27283787727355957s
Reputation | Calculation of the PageRank for JEL Classification took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for JEL Classification took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for JEL Classification took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.8133392333984375e-05s
Believability | Calculation of trust value for JEL Classification took 6.9141387939453125e-06s
INFO | --- Analysis for jel-classification took 4.743325710296631s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.183223009109497s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.26264309883117676s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020423412322998047s
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.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 8.58306884765625e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 7.7182581424713135s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.8777358531952s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0003409385681152344s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.28584957122802734s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.022326946258544922s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.000789642333984375s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.320808410644531e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 1.0728836059570312e-05s
INFO | --- Analysis for jita took 540.6663179397583s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.3392181396484375e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.2674548625946045s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020684480667114258s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 4.220008850097656e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.867813110351562e-06s
INFO | --- Analysis for jmdict took 3.918984889984131s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.071561336517334s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0006425380706787109s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.7179639339447021s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.202957153320312e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 8.58306884765625e-06s
INFO | --- Analysis for john-goodwins-family-tree took 63.961944341659546s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.38690185546875e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.7675988674163818s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0007529258728027344s
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 7.152557373046875e-06s
INFO | --- Analysis for jp-cos took 5.775795221328735s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.8160552978515625e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0006918907165527344s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.29999732971191406s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020643234252929688s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.910064697265625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.62939453125e-06s
INFO | --- Analysis for jp-textbook took 4.363762140274048s
Availability | SPARQL endpoint availability check for JRC-Names took 4.363059997558594e-05s
Availability | VoID file availability check for JRC-Names took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.26775026321411133s
Reputation | Calculation of the PageRank for JRC-Names took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for JRC-Names took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.314018249511719e-05s
Believability | Calculation of trust value for JRC-Names took 8.106231689453125e-06s
INFO | --- Analysis for jrc-names-ec took 5.359479904174805s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 0.9918327331542969s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.27272701263427734s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.961822509765625e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 8.106231689453125e-06s
INFO | --- Analysis for jrc-names-mlode took 4.0195746421813965s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.38690185546875e-05s
Availability | VoID file availability check for JudaicaLink took 0.0007145404815673828s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.2693352699279785s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00010776519775390625s
Believability | Calculation of trust value for JudaicaLink took 6.9141387939453125e-06s
INFO | --- Analysis for judaicalink took 22.584024906158447s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 4.363059997558594e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.28161001205444336s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020734548568725586s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.266334533691406e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.1205673217773438e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 3.317359447479248s
Availability | SPARQL endpoint availability check for KAKEN took 5.6743621826171875e-05s
Availability | VoID file availability check for KAKEN took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for KAKEN took 0.2561068534851074s
Reputation | Calculation of the PageRank for KAKEN took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.147125244140625e-05s
Believability | Calculation of trust value for KAKEN took 7.867813110351562e-06s
INFO | --- Analysis for kaken took 2.949890613555908s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 0.07110714912414551s
Availability | VoID file availability check for Kallikratis municipalities took 0.00038909912109375s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2578723430633545s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.584426879882812e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 5.9604644775390625e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.4502370357513428s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.315376281738281e-05s
Availability | VoID file availability check for Openflights Routes took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.2521555423736572s
Reputation | Calculation of the PageRank for Openflights Routes took 0.021032094955444336s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 3.0994415283203125e-05s
Believability | Calculation of trust value for Openflights Routes took 6.198883056640625e-06s
INFO | --- Analysis for kasabi-openflights-routes took 2.903489112854004s
Availability | SPARQL endpoint availability check for EU Soccer League took 4.363059997558594e-05s
Availability | VoID file availability check for EU Soccer League took 0.0007276535034179688s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.2814185619354248s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.075599670410156e-05s
Believability | Calculation of trust value for EU Soccer League took 6.9141387939453125e-06s
INFO | --- Analysis for KG:Course_Submission took 3.4841060638427734s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.3392181396484375e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.0006670951843261719s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.2573246955871582s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.3113021850585938e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for KING took 2.579874277114868s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 5.3882598876953125e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0008542537689208984s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.27374720573425293s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020904064178466797s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0008156299591064453s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 8.106231689453125e-05s
Believability | Calculation of trust value for Klappstuhlclub took 6.198883056640625e-06s
INFO | --- Analysis for klappstuhlclub took 12.501136064529419s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 10.878027200698853s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.25525522232055664s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.02032327651977539s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.818771362304688e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 7.3909759521484375e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 23.31196641921997s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.0531158447265625e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.26321935653686523s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.8133392333984375e-05s
Believability | Calculation of trust value for Knowledge Forest took 7.152557373046875e-06s
INFO | --- Analysis for knowledge-map took 2.8715200424194336s
Availability | SPARQL endpoint availability check for Knowledge Forest took 5.984306335449219e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.26677966117858887s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.170967102050781e-05s
Believability | Calculation of trust value for Knowledge Forest took 5.7220458984375e-06s
INFO | --- Analysis for KnowledgeFusion took 2.3610308170318604s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.649162292480469e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.0006482601165771484s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.24145030975341797s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.020534515380859375s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.914138793945312e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 14.084747552871704s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 4.38690185546875e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.27901744842529297s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 6.67572021484375e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.8689894676208496s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.6253204345703125e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.2470548152923584s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020169496536254883s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.765655517578125e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.1205673217773438e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.33132004737854s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 4.0531158447265625e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.2783682346343994s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.02020859718322754s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.7418136596679688e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.3909759521484375e-06s
INFO | --- Analysis for ktr took 2.878567934036255s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.410743713378906e-05s
Availability | VoID file availability check for Informatics Studies took 0.0005278587341308594s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.25847363471984863s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.765655517578125e-05s
Believability | Calculation of trust value for Informatics Studies took 6.4373016357421875e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.9152562618255615s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 0.0658869743347168s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2684032917022705s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.020355701446533203s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.743171691894531e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 8.106231689453125e-06s
INFO | --- Analysis for kupkb took 8.484447956085205s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.1961669921875e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.27872347831726074s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 2.86102294921875e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 7.152557373046875e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.9570093154907227s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 10.218955278396606s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.2742793560028076s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020427942276000977s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 8.392333984375e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 8.106231689453125e-06s
INFO | --- Analysis for l3s-dblp took 48.61249780654907s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 23.679781198501587s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.28888416290283203s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.020441532135009766s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 7.176399230957031e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for lak-dataset took 67.22895097732544s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 0.2903103828430176s
Availability | VoID file availability check for  Language Name Authority List  took 0.0005359649658203125s
Extra | Recovery of all triples for  Language Name Authority List  took 93.09457612037659s
Amount of data | Number of triples check for  Language Name Authority List  took 0.6452569961547852s
Interoperability | New terms check for  Language Name Authority List  took 12.199891805648804s
Versatility | Languages check for  Language Name Authority List  took 300.0113263130188s
Interpretability | Number of blank nodes check for  Language Name Authority List  took 2.163369655609131s
Security | Check HTTPS for  Language Name Authority List  took 0.3693504333496094s
Interpretability | RDF structures check for  Language Name Authority List  took 0.36528444290161133s
Versatility | Serialization formats check for  Language Name Authority List  took 3.5327868461608887s
Availability | RDF dump link check for  Language Name Authority List  took 0.30076122283935547s
License | MR license check for  Language Name Authority List  took 0.13844060897827148s
License | HR license check for  Language Name Authority List  took 300.08373856544495s
Amount of data | Number of property check for  Language Name Authority List  took 0.19655609130859375s
Understandability | Number of label check for  Language Name Authority List  took 0.7515919208526611s
Understandability | URI regex check for  Language Name Authority List  took 0.22951507568359375s
Understandability | Vocabs check for  Language Name Authority List  took 0.09728193283081055s
Verifiability | Authors check for  Language Name Authority List  took 0.11389517784118652s
Verifiability | Publishers check for  Language Name Authority List  took 0.1422431468963623s
Performance | Throughput check for  Language Name Authority List  took 10.660303354263306s
Amount of data | Check the number of entities for  Language Name Authority List  took 0.00012302398681640625s
Verifiability | Contribs. check for  Language Name Authority List  took 0.0905916690826416s
Interlinking | sameAs chians check for  Language Name Authority List  took 0.9946975708007812s
Interlinking | skos check for  Language Name Authority List  took 0.3574049472808838s
Interlinking | skos check for  Language Name Authority List  took 0.13646245002746582s
Timeliness | dataset update frequency check for  Language Name Authority List  took 0.1800975799560547s
Currency | Creation date check for  Language Name Authority List  took 0.46207618713378906s
Currency | Modification date check for  Language Name Authority List  took 0.172074556350708s
Rep.Conc. | URIs length for  Language Name Authority List  took 111.69072389602661s
Interoperability | New vocabularies check for  Language Name Authority List  took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for  Language Name Authority List  took 0.13735127449035645s
Accuracy | Check Functional Property for  Language Name Authority List  took 0.1360492706298828s
Accuracy | Check Inverse Functional Property for  Language Name Authority List  took 0.1798698902130127s
Accuracy | Check Empty annotation labels for  Language Name Authority List  took 26.900965929031372s
Accuracy | Check White space in annotation for  Language Name Authority List  took 3.126354694366455s
Accuracy | Check Datatype consistency for  Language Name Authority List  took 2.619663953781128s
Consistency | Disjoint class check for  Language Name Authority List  took 0.16855740547180176s
Consistency | Check Misplaced properties for  Language Name Authority List  took 55.310970306396484s
Consistency | Misplaced classes for  Language Name Authority List  took 8.294048547744751s
Consistency | Check Ontology hijacking for  Language Name Authority List  took 31.042561292648315s
Consistency | Check Invalid usage of undefined classes for  Language Name Authority List  took 1.4039125442504883s
Consistency | Check Invalid usage of undefined properties for  Language Name Authority List  took 55.40394401550293s
Conciseness | Check Extensional conciseness for  Language Name Authority List  took 3.009550094604492s
Conciseness | Check Intensional conciseness for  Language Name Authority List  took 0.39008498191833496s
Security | Sign check for  Language Name Authority List  took 0.12169313430786133s
Availability | Check URIs Dereferenciability for  Language Name Authority List  took 9.148390054702759s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 2.109128952026367s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.020816564559936523s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for  Language Name Authority List  took 1.9073486328125e-06s
Believability | Calculation of trust value for  Language Name Authority List  took 6.9141387939453125e-06s
INFO | --- Analysis for language-authority-list took 13988.787658691406s
Availability | SPARQL endpoint availability check for Lark took 384.4132616519928s
Availability | VoID file availability check for Lark took 0.0007996559143066406s
Completeness | Calculation of interlinking completeness for Lark took 0.4379141330718994s
Reputation | Calculation of the PageRank for Lark took 0.02370929718017578s
Interlinking | Calculation of Degree of Connection for Lark took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Lark took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Lark took 7.843971252441406e-05s
Believability | Calculation of trust value for Lark took 7.152557373046875e-06s
INFO | --- Analysis for LARK took 1677.7991824150085s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 0.3646979331970215s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.00039386749267578125s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.27499842643737793s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020735979080200195s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for LASLA took 5.927972316741943s
Availability | SPARQL endpoint availability check for LATC Linksets took 4.410743713378906e-05s
Availability | VoID file availability check for LATC Linksets took 0.0003306865692138672s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.2525932788848877s
Reputation | Calculation of the PageRank for LATC Linksets took 0.02064657211303711s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0008478164672851562s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.218650817871094e-05s
Believability | Calculation of trust value for LATC Linksets took 7.3909759521484375e-06s
INFO | --- Analysis for latc-linksets took 3.8189520835876465s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 0.3893158435821533s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.23752474784851074s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 5.316734313964844e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 8.58306884765625e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 5.034486532211304s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 0.34918975830078125s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.00037860870361328125s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.26683688163757324s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.020639419555664062s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LatinAffectus took 5.2516913414001465s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.3485424518585205s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.2607138156890869s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007481575012207031s
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.62939453125e-06s
INFO | --- Analysis for LatinWordnetLiLa took 4.235435962677002s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.172325134277344e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.6758012771606445s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.1948089599609375e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 8.106231689453125e-06s
INFO | --- Analysis for lcc took 3.2279319763183594s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.363059997558594e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006625652313232422s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.36513686180114746s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02092289924621582s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00012493133544921875s
Believability | Calculation of trust value for Library of Congress Subject Headings took 8.344650268554688e-06s
INFO | --- Analysis for lcsh took 6.0770251750946045s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 8.20159912109375e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0006814002990722656s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.27262163162231445s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020663022994995117s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.606910705566406e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 8.106231689453125e-06s
INFO | --- Analysis for lcsubjects took 2.576856851577759s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.1484832763671875e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.25434279441833496s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.02042365074157715s
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.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.147125244140625e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 7.62939453125e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.921337127685547s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 9.318855047225952s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0006966590881347656s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.27257752418518066s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.021271228790283203s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0008590221405029297s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 6.031990051269531e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 7.867813110351562e-06s
INFO | --- Analysis for ldt@library took 36.998626470565796s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.1484832763671875e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.24368977546691895s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 3.0994415283203125e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 8.344650268554688e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.9784090518951416s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.553794860839844e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2512986660003662s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.3855438232421875e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 7.62939453125e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 3.0398552417755127s
Availability | SPARQL endpoint availability check for U ime Legije took 4.2438507080078125e-05s
Availability | VoID file availability check for U ime Legije took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.259810209274292s
Reputation | Calculation of the PageRank for U ime Legije took 0.020261764526367188s
Interlinking | Calculation of Degree of Connection for U ime Legije took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.86102294921875e-05s
Believability | Calculation of trust value for U ime Legije took 7.867813110351562e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.41839599609375s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.124641418457031e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.29238104820251465s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.0994415283203125e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 6.9141387939453125e-06s
INFO | --- Analysis for legislation-openuplabs took 2.9284088611602783s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 0.3475615978240967s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.29030418395996094s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020671606063842773s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.295608520507812e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 6.4373016357421875e-06s
INFO | --- Analysis for LemmaBank took 4.254532098770142s
Availability | SPARQL endpoint availability check for lemonUby took 4.4345855712890625e-05s
Availability | VoID file availability check for lemonUby took 0.0005741119384765625s
Completeness | Calculation of interlinking completeness for lemonUby took 0.2811586856842041s
Reputation | Calculation of the PageRank for lemonUby took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.508827209472656e-05s
Believability | Calculation of trust value for lemonUby took 6.9141387939453125e-06s
INFO | --- Analysis for lemonuby took 3.400862693786621s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.440017700195312e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0010759830474853516s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.26459550857543945s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.62396240234375e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.152557373046875e-06s
INFO | --- Analysis for lemonwiktionary took 4.138425350189209s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.3528597354888916s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.0006396770477294922s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.2763175964355469s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LewisShort took 3.7887258529663086s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 1.1510472297668457s
Availability | VoID file availability check for LEXIN-RDF took 0.0006058216094970703s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2756943702697754s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.02013874053955078s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.0040740966796875e-05s
Believability | Calculation of trust value for LEXIN-RDF took 7.152557373046875e-06s
INFO | --- Analysis for lexin-rdf took 5.746407985687256s
Availability | SPARQL endpoint availability check for lexinfo took 4.267692565917969e-05s
Availability | VoID file availability check for lexinfo took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for lexinfo took 0.2578911781311035s
Reputation | Calculation of the PageRank for lexinfo took 0.02056407928466797s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.96453857421875e-05s
Believability | Calculation of trust value for lexinfo took 6.9141387939453125e-06s
INFO | --- Analysis for lexinfo took 2.822080612182617s
Availability | SPARQL endpoint availability check for Lexvo took 4.410743713378906e-05s
Availability | VoID file availability check for Lexvo took 0.0007035732269287109s
Completeness | Calculation of interlinking completeness for Lexvo took 0.27010107040405273s
Reputation | Calculation of the PageRank for Lexvo took 0.020383596420288086s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017118453979492188s
Believability | Calculation of trust value for Lexvo took 7.3909759521484375e-06s
INFO | --- Analysis for lexvo took 42.61277961730957s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.2438507080078125e-05s
Availability | VoID file availability check for Lexvo.org took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.25072145462036133s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02067399024963379s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.700920104980469e-05s
Believability | Calculation of trust value for Lexvo.org took 1.1444091796875e-05s
INFO | --- Analysis for lexvo-org took 22.607600212097168s
Availability | SPARQL endpoint availability check for LIBRIS took 0.48203420639038086s
Availability | VoID file availability check for LIBRIS took 0.0006394386291503906s
Extra | Recovery of all triples for LIBRIS took 18.367050170898438s
Performance | Total latancy measurement for LIBRIS took 0.7257144451141357s
Amount of data | Number of triples check for LIBRIS took 23.07760190963745s
Interoperability | New terms check for LIBRIS took 14.357836246490479s
Versatility | Languages check for LIBRIS took 0.17728018760681152s
Interpretability | Number of blank nodes check for LIBRIS took 300.0745167732239s
Security | Check HTTPS for LIBRIS took 0.3769261837005615s
Interpretability | RDF structures check for LIBRIS took 0.4464554786682129s
Versatility | Serialization formats check for LIBRIS took 0.28446292877197266s
Availability | RDF dump link check for LIBRIS took 0.15265107154846191s
License | MR license check for LIBRIS took 0.36411571502685547s
License | HR license check for LIBRIS took 0.29169702529907227s
Amount of data | Number of property check for LIBRIS took 0.18858575820922852s
Understandability | Number of label check for LIBRIS took 0.765204906463623s
Understandability | URI regex check for LIBRIS took 0.4304323196411133s
Understandability | Vocabs check for LIBRIS took 0.1471850872039795s
Verifiability | Authors check for LIBRIS took 0.19552254676818848s
Verifiability | Publishers check for LIBRIS took 0.19245576858520508s
Performance | Throughput check for LIBRIS took 11.031888484954834s
Amount of data | Check the number of entities for LIBRIS took 7.414817810058594e-05s
Verifiability | Contribs. check for LIBRIS took 0.19866228103637695s
Interlinking | sameAs chians check for LIBRIS took 0.27324724197387695s
Interlinking | skos check for LIBRIS took 0.42969489097595215s
Interlinking | skos check for LIBRIS took 0.1393141746520996s
Timeliness | dataset update frequency check for LIBRIS took 0.16871142387390137s
Currency | Creation date check for LIBRIS took 0.3980977535247803s
Currency | Modification date check for LIBRIS took 0.6266529560089111s
Rep.Conc. | URIs length for LIBRIS took 83.0859682559967s
Interoperability | New vocabularies check for LIBRIS took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.19794130325317383s
Accuracy | Check Functional Property for LIBRIS took 0.1815803050994873s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.1504673957824707s
Accuracy | Check Datatype consistency for LIBRIS took 0.28251028060913086s
Consistency | Disjoint class check for LIBRIS took 0.18365955352783203s
Consistency | Check Misplaced properties for LIBRIS took 60.90121054649353s
Consistency | Misplaced classes for LIBRIS took 1.1568677425384521s
Consistency | Check Ontology hijacking for LIBRIS took 6.408624649047852s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3323137760162354s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 61.98305153846741s
Conciseness | Check Extensional conciseness for LIBRIS took 0.28717589378356934s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4046969413757324s
Security | Sign check for LIBRIS took 0.3354666233062744s
Availability | Check URIs Dereferenciability for LIBRIS took 10.112273931503296s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.7716507911682129s
Reputation | Calculation of the PageRank for LIBRIS took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 8.916854858398438e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 7.62939453125e-06s
INFO | --- Analysis for libris took 1090.1655037403107s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.06841635704040527s
Availability | VoID file availability check for Public Library of Veroia took 0.0007526874542236328s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.27455902099609375s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.02077031135559082s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 8.249282836914062e-05s
Believability | Calculation of trust value for Public Library of Veroia took 7.3909759521484375e-06s
INFO | --- Analysis for libver took 3.6727981567382812s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 0.2072761058807373s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00036907196044921875s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.7123274803161621s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.772445678710938e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 5.0067901611328125e-06s
INFO | --- Analysis for lichfield-spending took 4.2940404415130615s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.2438507080078125e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.001338958740234375s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.26244616508483887s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020377635955810547s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.2901763916015625e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.0251998901367188e-05s
INFO | --- Analysis for lime took 7.327370882034302s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.458427429199219e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006017684936523438s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.2746303081512451s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020435571670532227s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010538101196289062s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 7.62939453125e-06s
INFO | --- Analysis for lingvoj took 7.804964303970337s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 5.269050598144531e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.2503693103790283s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 8.177757263183594e-05s
Believability | Calculation of trust value for Linked Crunchbase took 7.152557373046875e-06s
INFO | --- Analysis for linked-crunchbase took 2.7712512016296387s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.282167434692383s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2512962818145752s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02040243148803711s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.152557373046875e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.5367431640625e-06s
INFO | --- Analysis for linked-drugs took 20.756224393844604s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.458427429199219e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.259657621383667s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.703636169433594e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 4.5299530029296875e-06s
INFO | --- Analysis for linked-edgar took 4.107674598693848s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.410743713378906e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.2595973014831543s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.02034306526184082s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 0.00011420249938964844s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 6.4373016357421875e-06s
INFO | --- Analysis for linked-eurostat took 4.025727033615112s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.363059997558594e-05s
Availability | VoID file availability check for linked hypernyms took 0.0006043910980224609s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.25166845321655273s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.462501525878906e-05s
Believability | Calculation of trust value for linked hypernyms took 7.3909759521484375e-06s
INFO | --- Analysis for linked-hypernyms took 3.2728354930877686s
Availability | SPARQL endpoint availability check for Linked Life Data took 208.0427713394165s
Availability | VoID file availability check for Linked Life Data took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.6486916542053223s
Reputation | Calculation of the PageRank for Linked Life Data took 0.021161556243896484s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0007760524749755859s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.839897155761719e-05s
Believability | Calculation of trust value for Linked Life Data took 7.152557373046875e-06s
INFO | --- Analysis for linked-life-data took 683.5051121711731s
Availability | SPARQL endpoint availability check for Linked Logainm took 0.3538527488708496s
Availability | VoID file availability check for Linked Logainm took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.6779861450195312s
Reputation | Calculation of the PageRank for Linked Logainm took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.2479248046875e-05s
Believability | Calculation of trust value for Linked Logainm took 6.9141387939453125e-06s
INFO | --- Analysis for linked-logainm took 5.138251543045044s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.291534423828125e-05s
Availability | VoID file availability check for Linked NUTS took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2566347122192383s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020892858505249023s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.125999450683594e-05s
Believability | Calculation of trust value for Linked NUTS took 6.198883056640625e-06s
INFO | --- Analysis for linked-nuts took 2.817885160446167s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 5.53131103515625e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.2794618606567383s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020230531692504883s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.9802322387695312e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 1.0728836059570312e-05s
INFO | --- Analysis for linked-open-aalto-data-service took 2.9599618911743164s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 1.8118903636932373s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.27481627464294434s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020437002182006836s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.4332275390625e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 5.245208740234375e-06s
INFO | --- Analysis for linked-open-camera took 4.386152982711792s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 3.9758028984069824s
Availability | VoID file availability check for Linked Open Commerce took 0.0006957054138183594s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.27872681617736816s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.7418136596679688e-05s
Believability | Calculation of trust value for Linked Open Commerce took 6.67572021484375e-06s
INFO | --- Analysis for linked-open-commerce took 12.775327920913696s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 2.0305986404418945s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.26849794387817383s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00011539459228515625s
Believability | Calculation of trust value for Linked Open Data of Ecology took 7.62939453125e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 4.514642715454102s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.3392181396484375e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2623023986816406s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.654594421386719e-05s
Believability | Calculation of trust value for Linked Open Numbers took 6.9141387939453125e-06s
INFO | --- Analysis for linked-open-numbers took 2.5800979137420654s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.0006334781646728516s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2575540542602539s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.021225929260253906s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0008382797241210938s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 4.0531158447265625e-05s
Believability | Calculation of trust value for Linked Open Piracy took 5.4836273193359375e-06s
INFO | --- Analysis for linked-open-piracy took 7.460530757904053s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.100799560546875e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.24096012115478516s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 7.152557373046875e-06s
INFO | --- Analysis for linked-open-senate took 2.8687171936035156s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 8.13918161392212s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.0006983280181884766s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.27100586891174316s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.9591064453125e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 8.344650268554688e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 33.581589221954346s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.315376281738281e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2716503143310547s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.910064697265625e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 4.76837158203125e-06s
INFO | --- Analysis for linked-periodicals took 3.0219156742095947s
Availability | SPARQL endpoint availability check for Linked Index took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Index took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2482764720916748s
Reputation | Calculation of the PageRank for Linked Index took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for Linked Index took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.320808410644531e-05s
Believability | Calculation of trust value for Linked Index took 7.3909759521484375e-06s
INFO | --- Analysis for linked-stockindex took 2.3796119689941406s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.789198637008667s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0006628036499023438s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.2598612308502197s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.02020430564880371s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.6716461181640625e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 6.9141387939453125e-06s
INFO | --- Analysis for linked-structured-product-labels took 12.67055606842041s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 0.9525291919708252s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.2744760513305664s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 7.62939453125e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 3.4814867973327637s
Availability | SPARQL endpoint availability check for Linked TCGA took 20.24462866783142s
Availability | VoID file availability check for Linked TCGA took 0.0006842613220214844s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.35041022300720215s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.511543273925781e-05s
Believability | Calculation of trust value for Linked TCGA took 7.867813110351562e-06s
INFO | --- Analysis for linked-tcga took 62.77334213256836s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.09645748138427734s
Availability | VoID file availability check for Linked User Feedback took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.27640819549560547s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.790855407714844e-05s
Believability | Calculation of trust value for Linked User Feedback took 6.4373016357421875e-06s
INFO | --- Analysis for linked-user-feedback took 2.4580941200256348s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.5299530029296875e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0012717247009277344s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.26928067207336426s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 8.511543273925781e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.152557373046875e-06s
INFO | --- Analysis for linked-uspto-patent-data took 53.331095933914185s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.696846008300781e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.26773715019226074s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020499229431152344s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007588863372802734s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 9.775161743164062e-06s
INFO | --- Analysis for linked-web-apis took 3.3424696922302246s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.220008850097656e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00039458274841308594s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.26239752769470215s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 2.8133392333984375e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 8.344650268554688e-06s
INFO | --- Analysis for linkedarc took 2.9171550273895264s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.07270550727844238s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0005781650543212891s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.27571725845336914s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.3855438232421875e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 8.106231689453125e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.740459442138672s
Availability | SPARQL endpoint availability check for LinkedCT took 1.498500108718872s
Availability | VoID file availability check for LinkedCT took 0.0006690025329589844s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.2844104766845703s
Reputation | Calculation of the PageRank for LinkedCT took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010514259338378906s
Believability | Calculation of trust value for LinkedCT took 7.867813110351562e-06s
INFO | --- Analysis for linkedct took 5.277791738510132s
Availability | SPARQL endpoint availability check for LinkedGeoData took 0.2227022647857666s
Availability | VoID file availability check for LinkedGeoData took 0.0005967617034912109s
Extra | Recovery of all triples for LinkedGeoData took 14.865150690078735s
Performance | Total latancy measurement for LinkedGeoData took 0.6972811222076416s
Amount of data | Number of triples check for LinkedGeoData took 44.78950548171997s
Interoperability | New terms check for LinkedGeoData took 91.55962347984314s
Versatility | Languages check for LinkedGeoData took 180.2806625366211s
Interpretability | Number of blank nodes check for LinkedGeoData took 0.20409321784973145s
Security | Check HTTPS for LinkedGeoData took 0.3309187889099121s
Interpretability | RDF structures check for LinkedGeoData took 0.1705334186553955s
Versatility | Serialization formats check for LinkedGeoData took 0.16491031646728516s
Availability | RDF dump link check for LinkedGeoData took 0.13118386268615723s
License | MR license check for LinkedGeoData took 0.12494444847106934s
License | HR license check for LinkedGeoData took 95.77400755882263s
Amount of data | Number of property check for LinkedGeoData took 0.16624140739440918s
Understandability | Number of label check for LinkedGeoData took 0.9834802150726318s
Understandability | URI regex check for LinkedGeoData took 0.31627488136291504s
Understandability | Vocabs check for LinkedGeoData took 0.15860676765441895s
Verifiability | Authors check for LinkedGeoData took 0.13898730278015137s
Verifiability | Publishers check for LinkedGeoData took 0.13119077682495117s
Performance | Throughput check for LinkedGeoData took 10.80144453048706s
Amount of data | Check the number of entities for LinkedGeoData took 0.06493067741394043s
Verifiability | Contribs. check for LinkedGeoData took 0.12593507766723633s
Interlinking | sameAs chians check for LinkedGeoData took 0.20352745056152344s
Interlinking | skos check for LinkedGeoData took 0.1633591651916504s
Interlinking | skos check for LinkedGeoData took 0.12406110763549805s
Timeliness | dataset update frequency check for LinkedGeoData took 0.14902043342590332s
Currency | Creation date check for LinkedGeoData took 0.2922189235687256s
Currency | Modification date check for LinkedGeoData took 0.2915356159210205s
Rep.Conc. | URIs length for LinkedGeoData took 272.8659121990204s
Interoperability | New vocabularies check for LinkedGeoData took 25.70969867706299s
Consistency | Deprecated classes/propertiers check for LinkedGeoData took 0.16723251342773438s
Accuracy | Check Functional Property for LinkedGeoData took 0.14845895767211914s
Accuracy | Check Inverse Functional Property for LinkedGeoData took 0.1320946216583252s
Accuracy | Check Empty annotation labels for LinkedGeoData took 2.9415228366851807s
Accuracy | Check White space in annotation for LinkedGeoData took 0.15908479690551758s
Accuracy | Check Datatype consistency for LinkedGeoData took 0.13514494895935059s
Consistency | Disjoint class check for LinkedGeoData took 0.15457987785339355s
Consistency | Check Misplaced properties for LinkedGeoData took 181.15950512886047s
Consistency | Misplaced classes for LinkedGeoData took 0.6411957740783691s
Consistency | Check Ontology hijacking for LinkedGeoData took 5.001099109649658s
Consistency | Check Invalid usage of undefined classes for LinkedGeoData took 1.2744274139404297s
Consistency | Check Invalid usage of undefined properties for LinkedGeoData took 181.69467687606812s
Conciseness | Check Extensional conciseness for LinkedGeoData took 0.15135431289672852s
Conciseness | Check Intensional conciseness for LinkedGeoData took 0.29052734375s
Security | Sign check for LinkedGeoData took 0.15570449829101562s
Availability | Check URIs Dereferenciability for LinkedGeoData took 12.032601356506348s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.9395473003387451s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.021120548248291016s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00012993812561035156s
Interoperability | Check the re-using of existing vocabs for LinkedGeoData took 73.91009783744812s
Believability | Calculation of trust value for LinkedGeoData took 6.9141387939453125e-06s
INFO | --- Analysis for linkedgeodata took 2249.258095264435s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 6.985664367675781e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.2763979434967041s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.600120544433594e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 6.67572021484375e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 4.773980140686035s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.03171968460083s
Availability | VoID file availability check for LinkedLCCN took 0.0007691383361816406s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.2696511745452881s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010752677917480469s
Believability | Calculation of trust value for LinkedLCCN took 6.67572021484375e-06s
INFO | --- Analysis for linkedlccn took 16.369528770446777s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.3392181396484375e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0006771087646484375s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.268878698348999s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0008261203765869141s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.743171691894531e-05s
Believability | Calculation of trust value for LinkedMarkMail took 6.67572021484375e-06s
INFO | --- Analysis for linkedmarkmail took 2.527271270751953s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 40.658655881881714s
Availability | VoID file availability check for Linked Movie DataBase took 0.0007991790771484375s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.26982808113098145s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0010001659393310547s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00016570091247558594s
Believability | Calculation of trust value for Linked Movie DataBase took 7.3909759521484375e-06s
INFO | --- Analysis for linkedmdb took 134.33610224723816s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.4683096408843994s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0011904239654541016s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.266141414642334s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02025914192199707s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.343292236328125e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for linkedspending took 4.051988363265991s
Availability | SPARQL endpoint availability check for LinkedStats took 4.1961669921875e-05s
Availability | VoID file availability check for LinkedStats took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.269197940826416s
Reputation | Calculation of the PageRank for LinkedStats took 0.021207571029663086s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.170967102050781e-05s
Believability | Calculation of trust value for LinkedStats took 6.67572021484375e-06s
INFO | --- Analysis for linkedstats took 3.7720792293548584s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 4.100799560546875e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2818472385406494s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.0040740966796875e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 7.62939453125e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.926189422607422s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.1484832763671875e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.29859161376953125s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007681846618652344s
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 7.62939453125e-06s
INFO | --- Analysis for linking-open-drug-data took 3.3919968605041504s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 0.053601980209350586s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.250169038772583s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.020266294479370117s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010919570922851562s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 6.9141387939453125e-06s
INFO | --- Analysis for linklion took 2.387281894683838s
Availability | SPARQL endpoint availability check for Lion's Den took 0.0005350112915039062s
Availability | VoID file availability check for Lion's Den took 0.00022459030151367188s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.27567076683044434s
Reputation | Calculation of the PageRank for Lion's Den took 0.02072739601135254s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.123283386230469e-05s
Believability | Calculation of trust value for Lion's Den took 6.67572021484375e-06s
INFO | --- Analysis for lionsden took 3.3347489833831787s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 38.023995876312256s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.7075319290161133s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.0067901611328125e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 7.152557373046875e-06s
INFO | --- Analysis for lista-encabezamientos-materia took 44.488940477371216s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.3392181396484375e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.2754204273223877s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.24249267578125e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.152557373046875e-06s
INFO | --- Analysis for livtdm took 3.3284051418304443s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 4.1961669921875e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.24184346199035645s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02054905891418457s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 2.7894973754882812e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 7.152557373046875e-06s
INFO | --- Analysis for livtdm2017 took 2.892731189727783s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.124641418457031e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.290388822555542s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 2.8371810913085938e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 6.9141387939453125e-06s
INFO | --- Analysis for lobi took 2.948366641998291s
Availability | SPARQL endpoint availability check for lobid-organisations took 1.1676392555236816s
Availability | VoID file availability check for lobid-organisations took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.26265907287597656s
Reputation | Calculation of the PageRank for lobid-organisations took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.632110595703125e-05s
Believability | Calculation of trust value for lobid-organisations took 7.62939453125e-06s
INFO | --- Analysis for lobid-organisations took 5.7769553661346436s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 0.9402697086334229s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0003020763397216797s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.24326682090759277s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020037412643432617s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.441375732421875e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 8.106231689453125e-06s
INFO | --- Analysis for lobid-resources took 8.207591772079468s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.38690185546875e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.26410675048828125s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.03143572807312012s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0013713836669921875s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 0.00012612342834472656s
Believability | Calculation of trust value for Linked Open Colors took 9.5367431640625e-06s
INFO | --- Analysis for loc took 7.238163232803345s
Availability | SPARQL endpoint availability check for Location Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for Location Ontology took 0.0006225109100341797s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.23825645446777344s
Reputation | Calculation of the PageRank for Location Ontology took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for Location Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Location Ontology took 6.67572021484375e-06s
INFO | --- Analysis for Location_Ontology took 3.496899127960205s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.220008850097656e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0005304813385009766s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.26607322692871094s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.123283386230469e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 6.9141387939453125e-06s
INFO | --- Analysis for locv took 37.3446524143219s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.7572968006134033s
Availability | VoID file availability check for LOD-a-lot took 0.0006699562072753906s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.26001715660095215s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.0517578125e-05s
Believability | Calculation of trust value for LOD-a-lot took 6.9141387939453125e-06s
INFO | --- Analysis for lod-a-lot took 14.440137386322021s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.1961669921875e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.2750077247619629s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020406246185302734s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.9067625999450684s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.27217936515808105s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 6.67572021484375e-06s
INFO | --- Analysis for lod-taiwan took 2.854574680328369s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.363059997558594e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0005197525024414062s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.2651832103729248s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020666837692260742s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.678436279296875e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 7.62939453125e-06s
INFO | --- Analysis for lod2-project-wiki took 3.620255708694458s
Availability | SPARQL endpoint availability check for LODAC BDLS took 2.9445624351501465s
Availability | VoID file availability check for LODAC BDLS took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.28751039505004883s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 7.200241088867188e-05s
Believability | Calculation of trust value for LODAC BDLS took 7.152557373046875e-06s
INFO | --- Analysis for lodac-bdls took 13.874757289886475s
Availability | SPARQL endpoint availability check for LODRussia Math took 4.1484832763671875e-05s
Availability | VoID file availability check for LODRussia Math took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.23574447631835938s
Reputation | Calculation of the PageRank for LODRussia Math took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.8848648071289062e-05s
Believability | Calculation of trust value for LODRussia Math took 6.67572021484375e-06s
INFO | --- Analysis for lodrussia-math took 2.8518295288085938s
Availability | SPARQL endpoint availability check for LODRussia Nano took 4.076957702636719e-05s
Availability | VoID file availability check for LODRussia Nano took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.2617065906524658s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020560741424560547s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.0279159545898438e-05s
Believability | Calculation of trust value for LODRussia Nano took 6.67572021484375e-06s
INFO | --- Analysis for lodrussia-nano took 2.902097702026367s
Availability | SPARQL endpoint availability check for LODStats took 4.220008850097656e-05s
Availability | VoID file availability check for LODStats took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for LODStats took 0.26288604736328125s
Reputation | Calculation of the PageRank for LODStats took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for LODStats took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for LODStats took 2.8371810913085938e-05s
Believability | Calculation of trust value for LODStats took 6.9141387939453125e-06s
INFO | --- Analysis for lodstats took 2.8828635215759277s
Availability | SPARQL endpoint availability check for LODUM took 4.57763671875e-05s
Availability | VoID file availability check for LODUM took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for LODUM took 0.2480473518371582s
Reputation | Calculation of the PageRank for LODUM took 0.0205078125s
Interlinking | Calculation of Degree of Connection for LODUM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for LODUM took 2.956390380859375e-05s
Believability | Calculation of trust value for LODUM took 7.152557373046875e-06s
INFO | --- Analysis for lodum took 2.8800125122070312s
Availability | SPARQL endpoint availability check for lofd took 0.13271093368530273s
Availability | VoID file availability check for lofd took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for lofd took 0.26766037940979004s
Reputation | Calculation of the PageRank for lofd took 0.020524263381958008s
Interlinking | Calculation of Degree of Connection for lofd took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for lofd took 2.956390380859375e-05s
Believability | Calculation of trust value for lofd took 6.9141387939453125e-06s
INFO | --- Analysis for lofd took 2.551659345626831s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 270.56050872802734s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.0007343292236328125s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.27216005325317383s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02077507972717285s
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.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.745887756347656e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 5.7220458984375e-06s
INFO | --- Analysis for loius took 584.6179568767548s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 4.3392181396484375e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.7322766780853271s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 3.7670135498046875e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.867813110351562e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 6.701227903366089s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 0.5936696529388428s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.3627958297729492s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020648479461669922s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 5.316734313964844e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 6.198883056640625e-06s
INFO | --- Analysis for london-gazette took 4.008491277694702s
Availability | SPARQL endpoint availability check for Weather Stations took 4.601478576660156e-05s
Availability | VoID file availability check for Weather Stations took 0.0007522106170654297s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.2516143321990967s
Reputation | Calculation of the PageRank for Weather Stations took 0.020160198211669922s
Interlinking | Calculation of Degree of Connection for Weather Stations took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 7.700920104980469e-05s
Believability | Calculation of trust value for Weather Stations took 9.5367431640625e-06s
INFO | --- Analysis for los_metar took 83.42312026023865s
Availability | SPARQL endpoint availability check for Lotico took 0.9269654750823975s
Availability | VoID file availability check for Lotico took 0.0006935596466064453s
Completeness | Calculation of interlinking completeness for Lotico took 0.2570929527282715s
Reputation | Calculation of the PageRank for Lotico took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for Lotico took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lotico took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Lotico took 7.939338684082031e-05s
Believability | Calculation of trust value for Lotico took 7.152557373046875e-06s
INFO | --- Analysis for lotico took 7.72637939453125s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 1.1423969268798828s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.0007693767547607422s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.241316556930542s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020233631134033203s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 2.9802322387695312e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.3113021850585938e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 9.493534088134766s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.525343656539917s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0002799034118652344s
Extra | Recovery of all triples for Polish Land Parcel Information System (LPIS) dataset @PSNC took 118.68312168121338s
Performance | Total latancy measurement for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.968242883682251s
Amount of data | Number of triples check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.0617094039917s
Interoperability | New terms check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 14.020554304122925s
Versatility | Languages check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.1490800380707s
Interpretability | Number of blank nodes check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.156558036804199s
Interpretability | RDF structures check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.22906041145324707s
Versatility | Serialization formats check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 10.368777513504028s
Availability | RDF dump link check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.26256394386291504s
License | MR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5550506114959717s
License | HR license check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 300.1642668247223s
Amount of data | Number of property check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3031177520751953s
Understandability | Number of label check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.8205337524414062s
Understandability | URI regex check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8227086067199707s
Understandability | Vocabs check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4221968650817871s
Verifiability | Authors check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.21550631523132324s
Verifiability | Publishers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2400352954864502s
Performance | Throughput check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 11.301755666732788s
Amount of data | Check the number of entities for Polish Land Parcel Information System (LPIS) dataset @PSNC took 5.650520324707031e-05s
Verifiability | Contribs. check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19902896881103516s
Interlinking | sameAs chians check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2114877700805664s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4716975688934326s
Interlinking | skos check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.4423549175262451s
Timeliness | dataset update frequency check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 6.325577259063721s
Currency | Creation date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.5011029243469238s
Currency | Modification date check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20714807510375977s
Rep.Conc. | URIs length for Polish Land Parcel Information System (LPIS) dataset @PSNC took 151.36882543563843s
Interoperability | New vocabularies check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.19702553749084473s
Accuracy | Check Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.3175337314605713s
Accuracy | Check Inverse Functional Property for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.2787027359008789s
Accuracy | Check Empty annotation labels for Polish Land Parcel Information System (LPIS) dataset @PSNC took 42.99402093887329s
Accuracy | Check White space in annotation for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6562838554382324s
Accuracy | Check Datatype consistency for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.614553213119507s
Consistency | Disjoint class check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.20484042167663574s
Consistency | Check Misplaced properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 83.05949354171753s
Consistency | Misplaced classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.432356119155884s
Consistency | Check Ontology hijacking for Polish Land Parcel Information System (LPIS) dataset @PSNC took 39.63919973373413s
Consistency | Check Invalid usage of undefined classes for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3514976501464844s
Consistency | Check Invalid usage of undefined properties for Polish Land Parcel Information System (LPIS) dataset @PSNC took 82.06885266304016s
Conciseness | Check Extensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.7491416931152344s
Conciseness | Check Intensional conciseness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.6820003986358643s
Security | Sign check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.8250913619995117s
Availability | Check URIs Dereferenciability for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.998117208480835s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.9425370693206787s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 3.910064697265625e-05s
Interoperability | Check the re-using of existing vocabs for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for LPIS_(Poland) took 2266.6883583068848s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.17757606506347656s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0002655982971191406s
Extra | Recovery of all triples for Land parcel dataset (LPIS) from Czech Republic @PSNC took 119.51474165916443s
Performance | Total latancy measurement for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.9760241508483887s
Amount of data | Number of triples check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.89027190208435s
Interoperability | New terms check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 14.718651294708252s
Versatility | Languages check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2579154968262s
Interpretability | Number of blank nodes check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.0640883445739746s
Interpretability | RDF structures check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.25992655754089355s
Versatility | Serialization formats check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.832415580749512s
Availability | RDF dump link check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3038508892059326s
License | MR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.6269207000732422s
License | HR license check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 300.2208788394928s
Amount of data | Number of property check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.44739723205566406s
Understandability | Number of label check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.661825656890869s
Understandability | URI regex check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.8225340843200684s
Understandability | Vocabs check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.43895554542541504s
Verifiability | Authors check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.1940901279449463s
Verifiability | Publishers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.2579803466796875s
Performance | Throughput check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 11.182220697402954s
Amount of data | Check the number of entities for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.605552673339844e-05s
Verifiability | Contribs. check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20540642738342285s
Interlinking | sameAs chians check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.20522737503051758s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.43152451515197754s
Interlinking | skos check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.46436238288879395s
Timeliness | dataset update frequency check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 7.047739267349243s
Currency | Creation date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.487898588180542s
Currency | Modification date check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.21763896942138672s
Rep.Conc. | URIs length for Land parcel dataset (LPIS) from Czech Republic @PSNC took 158.02756667137146s
Interoperability | New vocabularies check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18205022811889648s
Accuracy | Check Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3256337642669678s
Accuracy | Check Inverse Functional Property for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.3251652717590332s
Accuracy | Check Empty annotation labels for Land parcel dataset (LPIS) from Czech Republic @PSNC took 41.79479122161865s
Accuracy | Check White space in annotation for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.6675186157226562s
Accuracy | Check Datatype consistency for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7015609741210938s
Consistency | Disjoint class check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.19759011268615723s
Consistency | Check Misplaced properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 83.73161029815674s
Consistency | Misplaced classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.368877410888672s
Consistency | Check Ontology hijacking for Land parcel dataset (LPIS) from Czech Republic @PSNC took 40.77553129196167s
Consistency | Check Invalid usage of undefined classes for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.441413164138794s
Consistency | Check Invalid usage of undefined properties for Land parcel dataset (LPIS) from Czech Republic @PSNC took 81.24547123908997s
Conciseness | Check Extensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.835462808609009s
Conciseness | Check Intensional conciseness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.5563225746154785s
Security | Sign check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.17741131782531738s
Availability | Check URIs Dereferenciability for Land parcel dataset (LPIS) from Czech Republic @PSNC took 12.164906740188599s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.5479841232299805s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.600120544433594e-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 1.0728836059570312e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2274.0606410503387s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 4.7206878662109375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.00042176246643066406s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.27115464210510254s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020608186721801758s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 2.8848648071289062e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 7.3909759521484375e-06s
INFO | --- Analysis for lremap-auth took 5.269086599349976s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 4.291534423828125e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2946155071258545s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.020831823348999023s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.075599670410156e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 6.67572021484375e-06s
INFO | --- Analysis for lremap-conf took 3.985441207885742s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.649162292480469e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0005331039428710938s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.26549792289733887s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020206689834594727s
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.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.62396240234375e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 8.106231689453125e-06s
INFO | --- Analysis for lremap-ri took 3.5835464000701904s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00018453598022460938s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.7077450752258301s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.02040410041809082s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.218650817871094e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 8.106231689453125e-06s
INFO | --- Analysis for lremap-sub took 3.039381742477417s
Availability | SPARQL endpoint availability check for LSQ took 4.482269287109375e-05s
Availability | VoID file availability check for LSQ took 0.0006723403930664062s
Completeness | Calculation of interlinking completeness for LSQ took 0.6997051239013672s
Reputation | Calculation of the PageRank for LSQ took 0.021126747131347656s
Interlinking | Calculation of Degree of Connection for LSQ took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LSQ took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for LSQ took 2.956390380859375e-05s
Believability | Calculation of trust value for LSQ took 7.62939453125e-06s
INFO | --- Analysis for lsq took 4.133333921432495s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.5569155216217041s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0006725788116455078s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.30322933197021484s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for LucaniPharsalia took 4.158013820648193s
Availability | SPARQL endpoint availability check for Linked rules took 4.38690185546875e-05s
Availability | VoID file availability check for Linked rules took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Linked rules took 0.26110386848449707s
Reputation | Calculation of the PageRank for Linked rules took 0.020432233810424805s
Interlinking | Calculation of Degree of Connection for Linked rules took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked rules took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Linked rules took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linked rules took 7.62939453125e-06s
INFO | --- Analysis for Luminaires_senlis took 2.403510808944702s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.38690185546875e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.28080248832702637s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.037064313888549805s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.001544952392578125s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 4.5299530029296875e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 7.152557373046875e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.9003710746765137s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 30.31864643096924s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.00032782554626464844s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.25546932220458984s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.409385681152344e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for makg took 63.618491411209106s
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.0003337860107421875s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.27038049697875977s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.409385681152344e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 6.67572021484375e-06s
INFO | --- Analysis for manchester-university-reading-lists took 3.893998146057129s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.6253204345703125e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.26943397521972656s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.67572021484375e-06s
INFO | --- Analysis for manish took 2.5119380950927734s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.601478576660156e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.28336620330810547s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.8133392333984375e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 6.4373016357421875e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.933143377304077s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.673004150390625e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.29062771797180176s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 3.218650817871094e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 7.867813110351562e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.986103057861328s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.458427429199219e-05s
Availability | VoID file availability check for MARC Codes List took 0.0005986690521240234s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.3009345531463623s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020871400833129883s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0009965896606445312s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00014972686767578125s
Believability | Calculation of trust value for MARC Codes List took 8.106231689453125e-06s
INFO | --- Analysis for marc-codes took 14.56361174583435s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 7.104873657226562e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007250308990478516s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.29639267921447754s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.02072000503540039s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.1484832763671875e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for masc took 15.941455364227295s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.315376281738281e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.26439642906188965s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02037334442138672s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.981590270996094e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 6.67572021484375e-06s
INFO | --- Analysis for masc-bn-nif took 2.821969985961914s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.4309883117675781s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.3078904151916504s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.02056121826171875s
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.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.123283386230469e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.97501540184021s
Availability | SPARQL endpoint availability check for medline took 4.3392181396484375e-05s
Availability | VoID file availability check for medline took 0.0003268718719482422s
Completeness | Calculation of interlinking completeness for medline took 0.25906848907470703s
Reputation | Calculation of the PageRank for medline took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for medline took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for medline took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for medline took 3.552436828613281e-05s
Believability | Calculation of trust value for medline took 7.152557373046875e-06s
INFO | --- Analysis for medline took 7.149184942245483s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 2.7758677005767822s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0011909008026123047s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.3029763698577881s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0007624626159667969s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 7.104873657226562e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 8.344650268554688e-06s
INFO | --- Analysis for meducator took 15.64138150215149s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.410743713378906e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.2645556926727295s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.075599670410156e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 7.867813110351562e-06s
INFO | --- Analysis for mesh-finnish took 2.959747076034546s
Availability | SPARQL endpoint availability check for MeSH headings took 4.2438507080078125e-05s
Availability | VoID file availability check for MeSH headings took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.2800459861755371s
Reputation | Calculation of the PageRank for MeSH headings took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.0040740966796875e-05s
Believability | Calculation of trust value for MeSH headings took 7.62939453125e-06s
INFO | --- Analysis for mesh_headings took 2.954841375350952s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.315376281738281e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.2680680751800537s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.147125244140625e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.3909759521484375e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.934067487716675s
Availability | SPARQL endpoint availability check for MeSH pairs took 4.38690185546875e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2919802665710449s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020476579666137695s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.9087066650390625e-05s
Believability | Calculation of trust value for MeSH pairs took 7.152557373046875e-06s
INFO | --- Analysis for mesh_pairs took 2.971139669418335s
Availability | SPARQL endpoint availability check for MeSH titles took 5.745887756347656e-05s
Availability | VoID file availability check for MeSH titles took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.2682816982269287s
Reputation | Calculation of the PageRank for MeSH titles took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for MeSH titles took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.9325485229492188e-05s
Believability | Calculation of trust value for MeSH titles took 7.3909759521484375e-06s
INFO | --- Analysis for mesh_titles took 2.8949129581451416s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 8.702278137207031e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0007572174072265625s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2683877944946289s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.021099567413330078s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 3.0994415283203125e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 9.298324584960938e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.9137260913848877s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.38690185546875e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0003516674041748047s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.2752573490142822s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 2.956390380859375e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 7.152557373046875e-06s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 3.064565658569336s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 7.104873657226562e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.28022003173828125s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020920276641845703s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 8.392333984375e-05s
Believability | Calculation of trust value for MetaShare metadata model took 9.298324584960938e-06s
INFO | --- Analysis for metashare took 2.5547726154327393s
Availability | SPARQL endpoint availability check for MExiCo took 4.315376281738281e-05s
Availability | VoID file availability check for MExiCo took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for MExiCo took 0.27762937545776367s
Reputation | Calculation of the PageRank for MExiCo took 0.02057623863220215s
Interlinking | Calculation of Degree of Connection for MExiCo took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MExiCo took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.696846008300781e-05s
Believability | Calculation of trust value for MExiCo took 8.821487426757812e-06s
INFO | --- Analysis for mexico took 22.401817560195923s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 1.0318055152893066s
Availability | VoID file availability check for Coronavirus dataset took 0.00031685829162597656s
Extra | Recovery of all triples for Coronavirus dataset took 10.770286083221436s
Performance | Total latancy measurement for Coronavirus dataset took 2.4674432277679443s
Amount of data | Number of triples check for Coronavirus dataset took 1.152980089187622s
Interoperability | New terms check for Coronavirus dataset took 2.604076385498047s
Versatility | Languages check for Coronavirus dataset took 60.52578258514404s
Interpretability | Number of blank nodes check for Coronavirus dataset took 3.7310287952423096s
Interpretability | RDF structures check for Coronavirus dataset took 0.533494234085083s
Versatility | Serialization formats check for Coronavirus dataset took 0.5432994365692139s
Availability | RDF dump link check for Coronavirus dataset took 0.4976999759674072s
License | MR license check for Coronavirus dataset took 0.5626504421234131s
License | HR license check for Coronavirus dataset took 42.987088680267334s
Amount of data | Number of property check for Coronavirus dataset took 0.5347187519073486s
Understandability | Number of label check for Coronavirus dataset took 0.9759795665740967s
Understandability | URI regex check for Coronavirus dataset took 1.0049471855163574s
Understandability | Vocabs check for Coronavirus dataset took 0.5084214210510254s
Verifiability | Authors check for Coronavirus dataset took 0.5997512340545654s
Verifiability | Publishers check for Coronavirus dataset took 0.5100812911987305s
Performance | Throughput check for Coronavirus dataset took 14.290335416793823s
Amount of data | Check the number of entities for Coronavirus dataset took 7.534027099609375e-05s
Verifiability | Contribs. check for Coronavirus dataset took 0.5083613395690918s
Interlinking | sameAs chians check for Coronavirus dataset took 0.5343213081359863s
Interlinking | skos check for Coronavirus dataset took 0.5536911487579346s
Interlinking | skos check for Coronavirus dataset took 0.50119948387146s
Timeliness | dataset update frequency check for Coronavirus dataset took 0.5069634914398193s
Currency | Creation date check for Coronavirus dataset took 1.030247449874878s
Currency | Modification date check for Coronavirus dataset took 1.013357162475586s
Rep.Conc. | URIs length for Coronavirus dataset took 9.302697658538818s
Interoperability | New vocabularies check for Coronavirus dataset took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Coronavirus dataset took 0.5178542137145996s
Accuracy | Check Functional Property for Coronavirus dataset took 0.5706398487091064s
Accuracy | Check Inverse Functional Property for Coronavirus dataset took 0.7309167385101318s
Accuracy | Check Empty annotation labels for Coronavirus dataset took 2.3565142154693604s
Accuracy | Check White space in annotation for Coronavirus dataset took 0.022939443588256836s
Accuracy | Check Datatype consistency for Coronavirus dataset took 0.027815580368041992s
Consistency | Disjoint class check for Coronavirus dataset took 0.8453693389892578s
Consistency | Check Misplaced properties for Coronavirus dataset took 8.272027015686035s
Consistency | Misplaced classes for Coronavirus dataset took 0.6115567684173584s
Consistency | Check Ontology hijacking for Coronavirus dataset took 4.086297035217285s
Consistency | Check Invalid usage of undefined classes for Coronavirus dataset took 1.274787187576294s
Consistency | Check Invalid usage of undefined properties for Coronavirus dataset took 6.8568971157073975s
Conciseness | Check Extensional conciseness for Coronavirus dataset took 0.032042503356933594s
Conciseness | Check Intensional conciseness for Coronavirus dataset took 0.5334362983703613s
Security | Sign check for Coronavirus dataset took 0.5366363525390625s
Availability | Check URIs Dereferenciability for Coronavirus dataset took 3084.326506614685s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 1.0897979736328125s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.021190881729125977s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 2.2649765014648438e-05s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 0.00011944770812988281s
Interoperability | Check the re-using of existing vocabs for Coronavirus dataset took 1.9073486328125e-06s
Believability | Calculation of trust value for Coronavirus dataset took 6.9141387939453125e-06s
INFO | --- Analysis for micro-coronavirus took 3327.3420717716217s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.9604644775390625e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.29103994369506836s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.021383285522460938s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010704994201660156s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 6.243595361709595s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 5.3882598876953125e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0009357929229736328s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.6927900314331055s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011515617370605469s
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 9.837480306625366s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.12302780151367188s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0006890296936035156s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.3011741638183594s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.482269287109375e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.867813110351562e-06s
INFO | --- Analysis for mlsa took 4.174443006515503s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.3392181396484375e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0006549358367919922s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.24979281425476074s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.02049994468688965s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 6.67572021484375e-06s
INFO | --- Analysis for model took 35.07101798057556s
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.267692565917969e-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.0006914138793945312s
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.2803525924682617s
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.02061748504638672s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007414817810058594s
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.3855438232421875e-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.198883056640625e-06s
INFO | --- Analysis for model1 took 17.42318844795227s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.100799560546875e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.27684903144836426s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.02035355567932129s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.0279159545898438e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 6.67572021484375e-06s
INFO | --- Analysis for mond took 3.3900935649871826s
Availability | SPARQL endpoint availability check for MONDIS took 4.076957702636719e-05s
Availability | VoID file availability check for MONDIS took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for MONDIS took 0.29633331298828125s
Reputation | Calculation of the PageRank for MONDIS took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.9802322387695312e-05s
Believability | Calculation of trust value for MONDIS took 9.059906005859375e-06s
INFO | --- Analysis for mondis took 2.9528908729553223s
Availability | SPARQL endpoint availability check for Monumentos took 3.981590270996094e-05s
Availability | VoID file availability check for Monumentos took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for Monumentos took 0.706270694732666s
Reputation | Calculation of the PageRank for Monumentos took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Monumentos took 3.075599670410156e-05s
Believability | Calculation of trust value for Monumentos took 7.152557373046875e-06s
INFO | --- Analysis for monumentos-zaragoza took 3.40559983253479s
Availability | SPARQL endpoint availability check for MORElab took 1.0438497066497803s
Availability | VoID file availability check for MORElab took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for MORElab took 0.24753022193908691s
Reputation | Calculation of the PageRank for MORElab took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for MORElab took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for MORElab took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for MORElab took 0.00010275840759277344s
Believability | Calculation of trust value for MORElab took 1.5735626220703125e-05s
INFO | --- Analysis for morelab took 5.6460161209106445s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 11.08088755607605s
Availability | VoID file availability check for Mathematics Subject Classification took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.32417988777160645s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.344650268554688e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 7.3909759521484375e-06s
INFO | --- Analysis for msc took 19.740172863006592s
Availability | SPARQL endpoint availability check for Multext-East took 4.982948303222656e-05s
Availability | VoID file availability check for Multext-East took 0.0003781318664550781s
Completeness | Calculation of interlinking completeness for Multext-East took 0.28569674491882324s
Reputation | Calculation of the PageRank for Multext-East took 0.020650625228881836s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.457069396972656e-05s
Believability | Calculation of trust value for Multext-East took 7.152557373046875e-06s
INFO | --- Analysis for multext-east took 2.437588930130005s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.2438507080078125e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2741210460662842s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020762205123901367s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 3.504753112792969e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 8.106231689453125e-06s
INFO | --- Analysis for multilingualeulaw took 3.402217388153076s
Availability | SPARQL endpoint availability check for Multimedia Lab took 5.435943603515625e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.2886948585510254s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020840883255004883s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.695487976074219e-05s
Believability | Calculation of trust value for Multimedia Lab took 7.152557373046875e-06s
INFO | --- Analysis for multimedia-lab took 2.5416345596313477s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.00543212890625e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.2911829948425293s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.9325485229492188e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 8.821487426757812e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.9406979084014893s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.8219618797302246s
Availability | VoID file availability check for Muninn World War I took 0.0006940364837646484s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2781665325164795s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.893013000488281e-05s
Believability | Calculation of trust value for Muninn World War I took 7.867813110351562e-06s
INFO | --- Analysis for muninn-world-war-i took 11.014013051986694s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.38690185546875e-05s
Availability | VoID file availability check for Musei Italiani took 0.00029969215393066406s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.27305030822753906s
Reputation | Calculation of the PageRank for Musei Italiani took 0.02069258689880371s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0008268356323242188s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.9087066650390625e-05s
Believability | Calculation of trust value for Musei Italiani took 7.152557373046875e-06s
INFO | --- Analysis for musei-italiani took 2.9019863605499268s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 4.649162292480469e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.26216769218444824s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010538101196289062s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1444091796875e-05s
INFO | --- Analysis for museosespania-gnoss took 48.45424294471741s
Availability | SPARQL endpoint availability check for Italian Museums took 1.7366504669189453s
Availability | VoID file availability check for Italian Museums took 0.0005116462707519531s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.2549316883087158s
Reputation | Calculation of the PageRank for Italian Museums took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 9.393692016601562e-05s
Believability | Calculation of trust value for Italian Museums took 6.9141387939453125e-06s
INFO | --- Analysis for museums-in-italy took 4.186242341995239s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.4345855712890625e-05s
Availability | VoID file availability check for MusicBrainz took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2665832042694092s
Reputation | Calculation of the PageRank for MusicBrainz took 0.020206212997436523s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 2.8848648071289062e-05s
Believability | Calculation of trust value for MusicBrainz took 9.059906005859375e-06s
INFO | --- Analysis for musicbrainz_ took 2.8982534408569336s
Availability | SPARQL endpoint availability check for MusicNet Codex took 8.630752563476562e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002930164337158203s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.27905893325805664s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.021086454391479492s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.9802322387695312e-05s
Believability | Calculation of trust value for MusicNet Codex took 7.62939453125e-06s
INFO | --- Analysis for musicnet_codex took 3.0497751235961914s
Availability | SPARQL endpoint availability check for Muziekweb took 0.833439826965332s
Availability | VoID file availability check for Muziekweb took 0.0005404949188232422s
Extra | Recovery of all triples for Muziekweb took 1.9758851528167725s
Performance | Total latancy measurement for Muziekweb took 1.4081578254699707s
Amount of data | Number of triples check for Muziekweb took 0.3742251396179199s
Interoperability | New terms check for Muziekweb took 1.6930015087127686s
Versatility | Languages check for Muziekweb took 58.28018045425415s
Interpretability | Number of blank nodes check for Muziekweb took 0.3170433044433594s
Interpretability | RDF structures check for Muziekweb took 0.60489821434021s
Versatility | Serialization formats check for Muziekweb took 0.321749210357666s
Availability | RDF dump link check for Muziekweb took 0.28217649459838867s
License | MR license check for Muziekweb took 0.9248456954956055s
License | HR license check for Muziekweb took 16.23646354675293s
Amount of data | Number of property check for Muziekweb took 0.2663390636444092s
Understandability | Number of label check for Muziekweb took 0.3421323299407959s
Understandability | URI regex check for Muziekweb took 0.8342068195343018s
Understandability | Vocabs check for Muziekweb took 0.27777600288391113s
Verifiability | Authors check for Muziekweb took 0.3009500503540039s
Verifiability | Publishers check for Muziekweb took 0.3144404888153076s
Performance | Throughput check for Muziekweb took 11.383538961410522s
Amount of data | Check the number of entities for Muziekweb took 8.106231689453125e-05s
Verifiability | Contribs. check for Muziekweb took 0.3034512996673584s
Interlinking | sameAs chians check for Muziekweb took 0.290172815322876s
Interlinking | skos check for Muziekweb took 0.2855672836303711s
Interlinking | skos check for Muziekweb took 0.3050570487976074s
Timeliness | dataset update frequency check for Muziekweb took 0.305633544921875s
Currency | Creation date check for Muziekweb took 0.7602567672729492s
Currency | Modification date check for Muziekweb took 0.8194761276245117s
Rep.Conc. | URIs length for Muziekweb took 2.0121243000030518s
Interoperability | New vocabularies check for Muziekweb took 1.6689300537109375e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.29431962966918945s
Accuracy | Check Functional Property for Muziekweb took 0.5254125595092773s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5038928985595703s
Accuracy | Check Empty annotation labels for Muziekweb took 3.618199110031128s
Accuracy | Check White space in annotation for Muziekweb took 0.033977508544921875s
Accuracy | Check Datatype consistency for Muziekweb took 0.028968334197998047s
Consistency | Disjoint class check for Muziekweb took 0.4391021728515625s
Consistency | Check Misplaced properties for Muziekweb took 1.1453309059143066s
Consistency | Check Ontology hijacking for Muziekweb took 2.160001277923584s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.294945478439331s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.5966839790344238s
Conciseness | Check Extensional conciseness for Muziekweb took 0.032961368560791016s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3382256031036377s
Security | Sign check for Muziekweb took 0.3169405460357666s
Availability | Check URIs Dereferenciability for Muziekweb took 1861.4652676582336s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.400846004486084s
Reputation | Calculation of the PageRank for Muziekweb took 0.02109551429748535s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0008311271667480469s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 0.00012969970703125s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.6689300537109375e-06s
Believability | Calculation of trust value for Muziekweb took 7.152557373046875e-06s
INFO | --- Analysis for muziekweb took 2003.792622089386s
Availability | SPARQL endpoint availability check for myExperiment took 0.2986786365509033s
Availability | VoID file availability check for myExperiment took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for myExperiment took 0.24656963348388672s
Reputation | Calculation of the PageRank for myExperiment took 0.02022266387939453s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.703636169433594e-05s
Believability | Calculation of trust value for myExperiment took 6.9141387939453125e-06s
INFO | --- Analysis for my-experiment took 4.924367427825928s
Availability | SPARQL endpoint availability check for My Family Lineage took 0.0648343563079834s
Availability | VoID file availability check for My Family Lineage took 0.0003154277801513672s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2628023624420166s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.940696716308594e-05s
Believability | Calculation of trust value for My Family Lineage took 5.7220458984375e-06s
INFO | --- Analysis for my-family-lineage took 4.972657680511475s
Availability | SPARQL endpoint availability check for My ontology test took 0.4669489860534668s
Availability | VoID file availability check for My ontology test took 0.0010585784912109375s
Completeness | Calculation of interlinking completeness for My ontology test took 0.29447102546691895s
Reputation | Calculation of the PageRank for My ontology test took 0.021363258361816406s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.123283386230469e-05s
Believability | Calculation of trust value for My ontology test took 5.7220458984375e-06s
INFO | --- Analysis for myontologytest took 3.280647039413452s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 9.5367431640625e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.26619434356689453s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020160198211669922s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.870529174804688e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 8.821487426757812e-06s
INFO | --- Analysis for myopenlink-dataspaces took 3.1529700756073s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.29070782661438s
Availability | VoID file availability check for N-Lex as Linked Data took 0.0006151199340820312s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.29911351203918457s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.020806550979614258s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 7.486343383789062e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 5.4836273193359375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 12.108515739440918s
Availability | SPARQL endpoint availability check for NAICS 2007 took 25.749706983566284s
Availability | VoID file availability check for NAICS 2007 took 0.000835418701171875s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.2919352054595947s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.02063131332397461s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.409385681152344e-05s
Believability | Calculation of trust value for NAICS 2007 took 7.152557373046875e-06s
INFO | --- Analysis for naics-2007 took 126.5260112285614s
Availability | SPARQL endpoint availability check for NAICS 2012 took 24.382736682891846s
Availability | VoID file availability check for NAICS 2012 took 0.0008292198181152344s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.7028274536132812s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020711183547973633s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 5.555152893066406e-05s
Believability | Calculation of trust value for NAICS 2012 took 5.4836273193359375e-06s
INFO | --- Analysis for naics-2012 took 124.04251074790955s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.220008850097656e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.2665870189666748s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 4.935264587402344e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for nalt took 3.5824825763702393s
Availability | SPARQL endpoint availability check for Usernames  took 4.482269287109375e-05s
Availability | VoID file availability check for Usernames  took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Usernames  took 0.26195430755615234s
Reputation | Calculation of the PageRank for Usernames  took 0.020413637161254883s
Interlinking | Calculation of Degree of Connection for Usernames  took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Usernames  took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Usernames  took 2.9802322387695312e-05s
Believability | Calculation of trust value for Usernames  took 7.62939453125e-06s
INFO | --- Analysis for Names took 2.7534031867980957s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 1.7977197170257568s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.001138925552368164s
Extra | Recovery of all triples for Web NDL Authorities - National Diet Library of Japan took 1.0551271438598633s
Performance | Total latancy measurement for Web NDL Authorities - National Diet Library of Japan took 1.9869310855865479s
Amount of data | Number of triples check for Web NDL Authorities - National Diet Library of Japan took 13.043250560760498s
Interoperability | New terms check for Web NDL Authorities - National Diet Library of Japan took 29.185840606689453s
Versatility | Languages check for Web NDL Authorities - National Diet Library of Japan took 0.3829658031463623s
Interpretability | Number of blank nodes check for Web NDL Authorities - National Diet Library of Japan took 16.763102054595947s
Security | Check HTTPS for Web NDL Authorities - National Diet Library of Japan took 0.8542959690093994s
Interpretability | RDF structures check for Web NDL Authorities - National Diet Library of Japan took 0.36082935333251953s
Versatility | Serialization formats check for Web NDL Authorities - National Diet Library of Japan took 0.40985989570617676s
Availability | RDF dump link check for Web NDL Authorities - National Diet Library of Japan took 0.35100626945495605s
License | MR license check for Web NDL Authorities - National Diet Library of Japan took 0.391589879989624s
License | HR license check for Web NDL Authorities - National Diet Library of Japan took 91.82056498527527s
Amount of data | Number of property check for Web NDL Authorities - National Diet Library of Japan took 0.9435999393463135s
Understandability | Number of label check for Web NDL Authorities - National Diet Library of Japan took 8.879590511322021s
Understandability | URI regex check for Web NDL Authorities - National Diet Library of Japan took 0.8006880283355713s
Understandability | Vocabs check for Web NDL Authorities - National Diet Library of Japan took 0.41890954971313477s
Verifiability | Authors check for Web NDL Authorities - National Diet Library of Japan took 0.3793306350708008s
Verifiability | Publishers check for Web NDL Authorities - National Diet Library of Japan took 0.4107472896575928s
Performance | Throughput check for Web NDL Authorities - National Diet Library of Japan took 11.29837441444397s
Amount of data | Check the number of entities for Web NDL Authorities - National Diet Library of Japan took 3.933906555175781e-05s
Verifiability | Contribs. check for Web NDL Authorities - National Diet Library of Japan took 0.39911603927612305s
Interlinking | sameAs chians check for Web NDL Authorities - National Diet Library of Japan took 0.5712635517120361s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 2.4876809120178223s
Interlinking | skos check for Web NDL Authorities - National Diet Library of Japan took 1.1123287677764893s
Timeliness | dataset update frequency check for Web NDL Authorities - National Diet Library of Japan took 0.39060473442077637s
Currency | Creation date check for Web NDL Authorities - National Diet Library of Japan took 1.1336615085601807s
Currency | Modification date check for Web NDL Authorities - National Diet Library of Japan took 0.7136147022247314s
Rep.Conc. | URIs length for Web NDL Authorities - National Diet Library of Japan took 1.008962631225586s
Interoperability | New vocabularies check for Web NDL Authorities - National Diet Library of Japan took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for Web NDL Authorities - National Diet Library of Japan took 0.3375577926635742s
Accuracy | Check Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.411149263381958s
Accuracy | Check Inverse Functional Property for Web NDL Authorities - National Diet Library of Japan took 0.4065377712249756s
Accuracy | Check Empty annotation labels for Web NDL Authorities - National Diet Library of Japan took 0.3807046413421631s
Accuracy | Check White space in annotation for Web NDL Authorities - National Diet Library of Japan took 0.0003314018249511719s
Accuracy | Check Datatype consistency for Web NDL Authorities - National Diet Library of Japan took 0.0004856586456298828s
Consistency | Disjoint class check for Web NDL Authorities - National Diet Library of Japan took 0.3538241386413574s
Consistency | Check Misplaced properties for Web NDL Authorities - National Diet Library of Japan took 0.7601938247680664s
Consistency | Misplaced classes for Web NDL Authorities - National Diet Library of Japan took 0.36171388626098633s
Consistency | Check Ontology hijacking for Web NDL Authorities - National Diet Library of Japan took 1.7544808387756348s
Consistency | Check Invalid usage of undefined classes for Web NDL Authorities - National Diet Library of Japan took 1.3431766033172607s
Consistency | Check Invalid usage of undefined properties for Web NDL Authorities - National Diet Library of Japan took 1.7020573616027832s
Conciseness | Check Extensional conciseness for Web NDL Authorities - National Diet Library of Japan took 0.0006837844848632812s
Security | Sign check for Web NDL Authorities - National Diet Library of Japan took 0.376187801361084s
Availability | Check URIs Dereferenciability for Web NDL Authorities - National Diet Library of Japan took 3.670896291732788s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.26157546043395996s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 6.771087646484375e-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 6.198883056640625e-06s
INFO | --- Analysis for national-diet-library-authorities took 254.57180643081665s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 0.3922276496887207s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0005433559417724609s
Extra | Recovery of all triples for National Diet Library of Japan subject headings took 1.5090699195861816s
Performance | Total latancy measurement for National Diet Library of Japan subject headings took 1.8634276390075684s
Amount of data | Number of triples check for National Diet Library of Japan subject headings took 14.951828002929688s
Versatility | Languages check for National Diet Library of Japan subject headings took 0.8936831951141357s
Interpretability | Number of blank nodes check for National Diet Library of Japan subject headings took 18.939942836761475s
Security | Check HTTPS for National Diet Library of Japan subject headings took 0.3486521244049072s
Interpretability | RDF structures check for National Diet Library of Japan subject headings took 0.4041414260864258s
Versatility | Serialization formats check for National Diet Library of Japan subject headings took 0.4212324619293213s
Availability | RDF dump link check for National Diet Library of Japan subject headings took 0.40936279296875s
License | MR license check for National Diet Library of Japan subject headings took 0.3589937686920166s
License | HR license check for National Diet Library of Japan subject headings took 91.79823589324951s
Amount of data | Number of property check for National Diet Library of Japan subject headings took 0.8887608051300049s
Understandability | Number of label check for National Diet Library of Japan subject headings took 9.110779285430908s
Understandability | URI regex check for National Diet Library of Japan subject headings took 0.7942709922790527s
Understandability | Vocabs check for National Diet Library of Japan subject headings took 0.3708336353302002s
Verifiability | Authors check for National Diet Library of Japan subject headings took 0.3800945281982422s
Verifiability | Publishers check for National Diet Library of Japan subject headings took 0.3668813705444336s
Performance | Throughput check for National Diet Library of Japan subject headings took 11.378279685974121s
Amount of data | Check the number of entities for National Diet Library of Japan subject headings took 8.487701416015625e-05s
Verifiability | Contribs. check for National Diet Library of Japan subject headings took 0.39531612396240234s
Interlinking | sameAs chians check for National Diet Library of Japan subject headings took 0.5658400058746338s
Interlinking | skos check for National Diet Library of Japan subject headings took 2.502673625946045s
Interlinking | skos check for National Diet Library of Japan subject headings took 1.0830097198486328s
Timeliness | dataset update frequency check for National Diet Library of Japan subject headings took 0.35184311866760254s
Currency | Creation date check for National Diet Library of Japan subject headings took 1.095963478088379s
Currency | Modification date check for National Diet Library of Japan subject headings took 0.7748770713806152s
Rep.Conc. | URIs length for National Diet Library of Japan subject headings took 1.0329947471618652s
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.41554784774780273s
Accuracy | Check Functional Property for National Diet Library of Japan subject headings took 0.4009706974029541s
Accuracy | Check Inverse Functional Property for National Diet Library of Japan subject headings took 0.4095327854156494s
Accuracy | Check Empty annotation labels for National Diet Library of Japan subject headings took 0.3614645004272461s
Accuracy | Check White space in annotation for National Diet Library of Japan subject headings took 0.0007274150848388672s
Accuracy | Check Datatype consistency for National Diet Library of Japan subject headings took 0.0010364055633544922s
Consistency | Disjoint class check for National Diet Library of Japan subject headings took 0.38362622261047363s
Consistency | Check Misplaced properties for National Diet Library of Japan subject headings took 0.7716965675354004s
Consistency | Misplaced classes for National Diet Library of Japan subject headings took 0.39804744720458984s
Consistency | Check Ontology hijacking for National Diet Library of Japan subject headings took 1.7896571159362793s
Consistency | Check Invalid usage of undefined classes for National Diet Library of Japan subject headings took 1.3486430644989014s
Consistency | Check Invalid usage of undefined properties for National Diet Library of Japan subject headings took 1.7215709686279297s
Conciseness | Check Extensional conciseness for National Diet Library of Japan subject headings took 0.0006539821624755859s
Security | Sign check for National Diet Library of Japan subject headings took 0.35419797897338867s
Availability | Check URIs Dereferenciability for National Diet Library of Japan subject headings took 3.563668727874756s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.3345513343811035s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 6.246566772460938e-05s
Interoperability | Check the re-using of existing vocabs for National Diet Library of Japan subject headings took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.3909759521484375e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 317.9384434223175s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 0.9676306247711182s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0006923675537109375s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.7090537548065186s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.0203707218170166s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.172325134277344e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 7.3909759521484375e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 6.069900751113892s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.4345855712890625e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005564689636230469s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2695121765136719s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.723403930664062e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.9141387939453125e-06s
INFO | --- Analysis for Naturopathy took 3.957953691482544s
Availability | SPARQL endpoint availability check for Naturopathy took 4.172325134277344e-05s
Availability | VoID file availability check for Naturopathy took 0.00033283233642578125s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.2639899253845215s
Reputation | Calculation of the PageRank for Naturopathy took 0.021062135696411133s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 4.57763671875e-05s
Believability | Calculation of trust value for Naturopathy took 6.67572021484375e-06s
INFO | --- Analysis for naturopathy2 took 3.37850284576416s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 4.4345855712890625e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0003294944763183594s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.2774362564086914s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.314018249511719e-05s
Believability | Calculation of trust value for NCI Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for nci-thesaurus took 3.0399792194366455s
Availability | SPARQL endpoint availability check for COVID-19 Data took 3.405564546585083s
Availability | VoID file availability check for COVID-19 Data took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.26793551445007324s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020940065383911133s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for COVID-19 Data took 7.152557373046875e-06s
INFO | --- Analysis for NCMI-COVID-19 took 7.316042184829712s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 2.416761875152588s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.27300572395324707s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.33514404296875e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 7.152557373046875e-06s
INFO | --- Analysis for NCMICOVID-19 took 6.290053129196167s
Availability | SPARQL endpoint availability check for NDF-RT took 6.413459777832031e-05s
Availability | VoID file availability check for NDF-RT took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.25732994079589844s
Reputation | Calculation of the PageRank for NDF-RT took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.266334533691406e-05s
Believability | Calculation of trust value for NDF-RT took 7.152557373046875e-06s
INFO | --- Analysis for ndf-rt took 2.944352388381958s
Availability | SPARQL endpoint availability check for Near took 4.4345855712890625e-05s
Availability | VoID file availability check for Near took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Near took 0.25331902503967285s
Reputation | Calculation of the PageRank for Near took 0.020163774490356445s
Interlinking | Calculation of Degree of Connection for Near took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Near took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Near took 9.131431579589844e-05s
Believability | Calculation of trust value for Near took 6.67572021484375e-06s
INFO | --- Analysis for near took 9.359588384628296s
Availability | SPARQL endpoint availability check for Neel took 4.220008850097656e-05s
Availability | VoID file availability check for Neel took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Neel took 0.27402257919311523s
Reputation | Calculation of the PageRank for Neel took 0.020570993423461914s
Interlinking | Calculation of Degree of Connection for Neel took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neel took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Neel took 2.9087066650390625e-05s
Believability | Calculation of trust value for Neel took 8.106231689453125e-06s
INFO | --- Analysis for neel took 2.895063638687134s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.363059997558594e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.27557921409606934s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020693540573120117s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.0040740966796875e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 1.2159347534179688e-05s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.930227041244507s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.4345855712890625e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.2652931213378906s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.02161407470703125s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007631778717041016s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.4809112548828125e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 9.775161743164062e-06s
INFO | --- Analysis for neurolex-wiki took 2.5009655952453613s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.4345855712890625e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0006287097930908203s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.27222681045532227s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020513057708740234s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.4345855712890625e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 7.62939453125e-06s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 3.4858157634735107s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.363059997558594e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0005939006805419922s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.2675478458404541s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 9.298324584960938e-06s
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.699562072753906e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 4.123876333236694s
Availability | SPARQL endpoint availability check for Newsweek took 4.1484832763671875e-05s
Availability | VoID file availability check for Newsweek took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Newsweek took 0.24422478675842285s
Reputation | Calculation of the PageRank for Newsweek took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for Newsweek took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Newsweek took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.9325485229492188e-05s
Believability | Calculation of trust value for Newsweek took 7.3909759521484375e-06s
INFO | --- Analysis for newsweek took 2.893902063369751s
Availability | SPARQL endpoint availability check for neXtProt took 1.60258150100708s
Availability | VoID file availability check for neXtProt took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for neXtProt took 0.24870967864990234s
Reputation | Calculation of the PageRank for neXtProt took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.6716461181640625e-05s
Believability | Calculation of trust value for neXtProt took 7.3909759521484375e-06s
INFO | --- Analysis for nextprot took 4.651320695877075s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.4345855712890625e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00064849853515625s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.2851874828338623s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020528793334960938s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010848045349121094s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 6.67572021484375e-06s
INFO | --- Analysis for nextweb-gnoss took 10.16765570640564s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.3392181396484375e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.24572515487670898s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.022502899169921875s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 9.083747863769531e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 5.245208740234375e-06s
INFO | --- Analysis for nhs-jargon took 2.8207523822784424s
Availability | SPARQL endpoint availability check for NIT Patna took 4.410743713378906e-05s
Availability | VoID file availability check for NIT Patna took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.24297738075256348s
Reputation | Calculation of the PageRank for NIT Patna took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for NIT Patna took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.556510925292969e-05s
Believability | Calculation of trust value for NIT Patna took 7.152557373046875e-06s
INFO | --- Analysis for NITP took 3.29093861579895s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 5.221366882324219e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.23722624778747559s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.6716461181640625e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 7.152557373046875e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.91941499710083s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.291534423828125e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.26422810554504395s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02059197425842285s
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.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 2.8371810913085938e-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.069226264953613s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 0.5176305770874023s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.27315592765808105s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.910064697265625e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for NLW took 3.801511287689209s
Availability | SPARQL endpoint availability check for Nobel Prizes took 3.4003703594207764s
Availability | VoID file availability check for Nobel Prizes took 0.0006031990051269531s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.26673078536987305s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 9.465217590332031e-05s
Believability | Calculation of trust value for Nobel Prizes took 8.106231689453125e-06s
INFO | --- Analysis for nobelprizes took 8.395287990570068s
Availability | SPARQL endpoint availability check for NoiPA took 0.32045912742614746s
Availability | VoID file availability check for NoiPA took 0.0002753734588623047s
Extra | Recovery of all triples for NoiPA took 74.82058811187744s
Performance | Total latancy measurement for NoiPA took 0.9729859828948975s
Amount of data | Number of triples check for NoiPA took 1.5728247165679932s
Interoperability | New terms check for NoiPA took 2.9427998065948486s
Versatility | Languages check for NoiPA took 0.11896038055419922s
Interpretability | Number of blank nodes check for NoiPA took 0.24535250663757324s
Interpretability | RDF structures check for NoiPA took 0.25942349433898926s
Versatility | Serialization formats check for NoiPA took 0.15897631645202637s
Availability | RDF dump link check for NoiPA took 0.20591998100280762s
License | MR license check for NoiPA took 0.80245041847229s
License | HR license check for NoiPA took 60.28826594352722s
Amount of data | Number of property check for NoiPA took 0.22957301139831543s
Understandability | Number of label check for NoiPA took 0.7625637054443359s
Understandability | URI regex check for NoiPA took 0.4273970127105713s
Understandability | Vocabs check for NoiPA took 0.15932083129882812s
Verifiability | Authors check for NoiPA took 0.13233137130737305s
Verifiability | Publishers check for NoiPA took 0.1549980640411377s
Performance | Throughput check for NoiPA took 10.619320631027222s
Amount of data | Check the number of entities for NoiPA took 3.4332275390625e-05s
Verifiability | Contribs. check for NoiPA took 0.14884185791015625s
Interlinking | sameAs chians check for NoiPA took 0.12975168228149414s
Interlinking | skos check for NoiPA took 0.7628400325775146s
Interlinking | skos check for NoiPA took 0.0903630256652832s
Timeliness | dataset update frequency check for NoiPA took 0.15176701545715332s
Currency | Creation date check for NoiPA took 0.2577180862426758s
Currency | Modification date check for NoiPA took 0.09869790077209473s
Rep.Conc. | URIs length for NoiPA took 50.034119844436646s
Interoperability | New vocabularies check for NoiPA took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for NoiPA took 0.23659396171569824s
Accuracy | Check Functional Property for NoiPA took 0.28450870513916016s
Accuracy | Check Inverse Functional Property for NoiPA took 0.180922269821167s
Accuracy | Check Empty annotation labels for NoiPA took 29.132248401641846s
Accuracy | Check White space in annotation for NoiPA took 2.248838424682617s
Accuracy | Check Datatype consistency for NoiPA took 1.9779813289642334s
Consistency | Disjoint class check for NoiPA took 0.22559428215026855s
Consistency | Check Misplaced properties for NoiPA took 18.524247646331787s
Consistency | Misplaced classes for NoiPA took 6.31769585609436s
Consistency | Check Ontology hijacking for NoiPA took 28.10494565963745s
Consistency | Check Invalid usage of undefined classes for NoiPA took 1.634007215499878s
Consistency | Check Invalid usage of undefined properties for NoiPA took 19.80720043182373s
Conciseness | Check Extensional conciseness for NoiPA took 2.1818907260894775s
Conciseness | Check Intensional conciseness for NoiPA took 0.1897733211517334s
Security | Sign check for NoiPA took 0.19859576225280762s
Availability | Check URIs Dereferenciability for NoiPA took 13.469283103942871s
Completeness | Calculation of interlinking completeness for NoiPA took 0.5255804061889648s
Reputation | Calculation of the PageRank for NoiPA took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for NoiPA took 1.9073486328125e-06s
Believability | Calculation of trust value for NoiPA took 8.344650268554688e-06s
INFO | --- Analysis for NoiPA took 465.74122309684753s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 6.457825183868408s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0006165504455566406s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.27695417404174805s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02063608169555664s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 8.940696716308594e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 7.867813110351562e-06s
INFO | --- Analysis for nom took 23.562060594558716s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 24.90798854827881s
Availability | VoID file availability check for Nomenclator Asturias took 0.0008845329284667969s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.7180356979370117s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.0214385986328125s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 8.082389831542969e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 5.245208740234375e-06s
INFO | --- Analysis for nomenclator-asturias took 138.26114797592163s
Availability | SPARQL endpoint availability check for nomisma took 4.1484832763671875e-05s
Availability | VoID file availability check for nomisma took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for nomisma took 0.2701420783996582s
Reputation | Calculation of the PageRank for nomisma took 0.020341157913208008s
Interlinking | Calculation of Degree of Connection for nomisma took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for nomisma took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.86102294921875e-05s
Believability | Calculation of trust value for nomisma took 7.867813110351562e-06s
INFO | --- Analysis for nomisma took 3.9994935989379883s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4463326930999756s
Availability | VoID file availability check for Nomisma.org  took 0.0005602836608886719s
Extra | Recovery of all triples for Nomisma.org  took 824.4615919589996s
Performance | Total latancy measurement for Nomisma.org  took 1.6912901401519775s
Amount of data | Number of triples check for Nomisma.org  took 43.926395654678345s
Interoperability | New terms check for Nomisma.org  took 8.978492259979248s
Versatility | Languages check for Nomisma.org  took 103.5676691532135s
Interpretability | Number of blank nodes check for Nomisma.org  took 31.46334457397461s
Security | Check HTTPS for Nomisma.org  took 0.7634530067443848s
Interpretability | RDF structures check for Nomisma.org  took 0.3507506847381592s
Versatility | Serialization formats check for Nomisma.org  took 0.34574151039123535s
Availability | RDF dump link check for Nomisma.org  took 887.5206134319305s
License | MR license check for Nomisma.org  took 0.37610697746276855s
License | HR license check for Nomisma.org  took 59.44116735458374s
Amount of data | Number of property check for Nomisma.org  took 0.37488317489624023s
Understandability | Number of label check for Nomisma.org  took 9.79473328590393s
Understandability | URI regex check for Nomisma.org  took 0.6766552925109863s
Understandability | Vocabs check for Nomisma.org  took 0.31441640853881836s
Verifiability | Authors check for Nomisma.org  took 0.3226180076599121s
Verifiability | Publishers check for Nomisma.org  took 0.36684250831604004s
Performance | Throughput check for Nomisma.org  took 12.616599798202515s
Amount of data | Check the number of entities for Nomisma.org  took 60.34192180633545s
Verifiability | Contribs. check for Nomisma.org  took 0.38724708557128906s
Interlinking | sameAs chians check for Nomisma.org  took 0.3606758117675781s
Interlinking | skos check for Nomisma.org  took 1.0366551876068115s
Interlinking | skos check for Nomisma.org  took 0.4876542091369629s
Timeliness | dataset update frequency check for Nomisma.org  took 0.35628628730773926s
Currency | Creation date check for Nomisma.org  took 0.7029154300689697s
Currency | Modification date check for Nomisma.org  took 0.3652763366699219s
Rep.Conc. | URIs length for Nomisma.org  took 344.7330813407898s
Interoperability | New vocabularies check for Nomisma.org  took 9.775161743164062e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.3646585941314697s
Accuracy | Check Functional Property for Nomisma.org  took 0.39510297775268555s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.3209528923034668s
Accuracy | Check Empty annotation labels for Nomisma.org  took 306.4770128726959s
Accuracy | Check White space in annotation for Nomisma.org  took 2.757174253463745s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.423159837722778s
Consistency | Disjoint class check for Nomisma.org  took 0.38120126724243164s
Consistency | Check Misplaced properties for Nomisma.org  took 25.021960973739624s
Consistency | Check Ontology hijacking for Nomisma.org  took 276.5829734802246s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 1.9413933753967285s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 27.226327896118164s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.799569606781006s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.6640591621398926s
Security | Sign check for Nomisma.org  took 0.39475488662719727s
Availability | Check URIs Dereferenciability for Nomisma.org  took 1730.5340383052826s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.6516947746276855s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 6.127357482910156e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 3.5762786865234375e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.3828277587890625e-05s
INFO | --- Analysis for nomisma_org took 9018.385539770126s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 0.43308377265930176s
Availability | VoID file availability check for Curriculum Vitae took 0.0002524852752685547s
Extra | Recovery of all triples for Curriculum Vitae took 0.707054615020752s
Performance | Total latancy measurement for Curriculum Vitae took 1.68495774269104s
Amount of data | Number of triples check for Curriculum Vitae took 0.1410064697265625s
Interoperability | New terms check for Curriculum Vitae took 1.5550737380981445s
Versatility | Languages check for Curriculum Vitae took 0.11563324928283691s
Interpretability | Number of blank nodes check for Curriculum Vitae took 0.1350243091583252s
Interpretability | RDF structures check for Curriculum Vitae took 0.24251937866210938s
Versatility | Serialization formats check for Curriculum Vitae took 0.23720359802246094s
Availability | RDF dump link check for Curriculum Vitae took 0.26212286949157715s
License | MR license check for Curriculum Vitae took 0.25681018829345703s
License | HR license check for Curriculum Vitae took 0.2527754306793213s
Amount of data | Number of property check for Curriculum Vitae took 0.290341854095459s
Understandability | Number of label check for Curriculum Vitae took 0.1276407241821289s
Understandability | URI regex check for Curriculum Vitae took 0.5504105091094971s
Understandability | Vocabs check for Curriculum Vitae took 0.2730696201324463s
Verifiability | Authors check for Curriculum Vitae took 0.27148866653442383s
Verifiability | Publishers check for Curriculum Vitae took 0.13595914840698242s
Performance | Throughput check for Curriculum Vitae took 10.939888954162598s
Amount of data | Check the number of entities for Curriculum Vitae took 0.00010967254638671875s
Verifiability | Contribs. check for Curriculum Vitae took 0.3486626148223877s
Interlinking | sameAs chians check for Curriculum Vitae took 0.26842308044433594s
Interlinking | skos check for Curriculum Vitae took 0.11391425132751465s
Interlinking | skos check for Curriculum Vitae took 0.23947501182556152s
Timeliness | dataset update frequency check for Curriculum Vitae took 0.12533068656921387s
Currency | Creation date check for Curriculum Vitae took 0.2643005847930908s
Currency | Modification date check for Curriculum Vitae took 0.33998680114746094s
Rep.Conc. | URIs length for Curriculum Vitae took 0.696361780166626s
Interoperability | New vocabularies check for Curriculum Vitae took 7.152557373046875e-07s
Consistency | Deprecated classes/propertiers check for Curriculum Vitae took 0.1346752643585205s
Accuracy | Check Functional Property for Curriculum Vitae took 0.11257696151733398s
Accuracy | Check Inverse Functional Property for Curriculum Vitae took 0.22524762153625488s
Accuracy | Check Empty annotation labels for Curriculum Vitae took 0.12951898574829102s
Accuracy | Check White space in annotation for Curriculum Vitae took 0.00010061264038085938s
Accuracy | Check Datatype consistency for Curriculum Vitae took 0.0032417774200439453s
Consistency | Disjoint class check for Curriculum Vitae took 0.23735308647155762s
Consistency | Check Misplaced properties for Curriculum Vitae took 0.500044584274292s
Consistency | Check Ontology hijacking for Curriculum Vitae took 1.849266529083252s
Consistency | Check Invalid usage of undefined classes for Curriculum Vitae took 1.702803373336792s
Consistency | Check Invalid usage of undefined properties for Curriculum Vitae took 2.0127947330474854s
Conciseness | Check Extensional conciseness for Curriculum Vitae took 0.0014405250549316406s
Security | Sign check for Curriculum Vitae took 0.12330746650695801s
Availability | Check URIs Dereferenciability for Curriculum Vitae took 21.319538354873657s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.28029656410217285s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.021315336227416992s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0009996891021728516s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 4.0531158447265625e-05s
Interoperability | Check the re-using of existing vocabs for Curriculum Vitae took 2.384185791015625e-06s
Believability | Calculation of trust value for Curriculum Vitae took 8.106231689453125e-06s
INFO | --- Analysis for Nordine_Bittich took 64.40512371063232s
Availability | SPARQL endpoint availability check for NorPark took 0.478971004486084s
Availability | VoID file availability check for NorPark took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for NorPark took 0.2803223133087158s
Reputation | Calculation of the PageRank for NorPark took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for NorPark took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NorPark took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.57763671875e-05s
Believability | Calculation of trust value for NorPark took 1.33514404296875e-05s
INFO | --- Analysis for norpark took 5.096451044082642s
Availability | SPARQL endpoint availability check for Parking Dataset took 0.022450685501098633s
Availability | VoID file availability check for Parking Dataset took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.7213258743286133s
Reputation | Calculation of the PageRank for Parking Dataset took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0009658336639404297s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 5.3882598876953125e-05s
Believability | Calculation of trust value for Parking Dataset took 8.821487426757812e-06s
INFO | --- Analysis for norpark2 took 4.686150550842285s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 0.5784742832183838s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0002608299255371094s
Extra | Recovery of all triples for Norway fishery stocks dataset took 127.1632776260376s
Performance | Total latancy measurement for Norway fishery stocks dataset took 0.9906914234161377s
Amount of data | Number of triples check for Norway fishery stocks dataset took 8.136234283447266s
Interoperability | New terms check for Norway fishery stocks dataset took 18.78421711921692s
Versatility | Languages check for Norway fishery stocks dataset took 300.24085760116577s
Interpretability | Number of blank nodes check for Norway fishery stocks dataset took 3.2690064907073975s
Interpretability | RDF structures check for Norway fishery stocks dataset took 0.27925610542297363s
Versatility | Serialization formats check for Norway fishery stocks dataset took 10.036028146743774s
Availability | RDF dump link check for Norway fishery stocks dataset took 0.26073741912841797s
License | MR license check for Norway fishery stocks dataset took 0.5424108505249023s
License | HR license check for Norway fishery stocks dataset took 300.2091462612152s
Amount of data | Number of property check for Norway fishery stocks dataset took 0.32069993019104004s
Understandability | Number of label check for Norway fishery stocks dataset took 2.7104134559631348s
Understandability | URI regex check for Norway fishery stocks dataset took 0.7971014976501465s
Understandability | Vocabs check for Norway fishery stocks dataset took 0.4430363178253174s
Verifiability | Authors check for Norway fishery stocks dataset took 0.19810962677001953s
Verifiability | Publishers check for Norway fishery stocks dataset took 0.25607967376708984s
Performance | Throughput check for Norway fishery stocks dataset took 10.788841485977173s
Amount of data | Check the number of entities for Norway fishery stocks dataset took 3.337860107421875e-05s
Verifiability | Contribs. check for Norway fishery stocks dataset took 0.21586060523986816s
Interlinking | sameAs chians check for Norway fishery stocks dataset took 0.1866903305053711s
Interlinking | skos check for Norway fishery stocks dataset took 0.465221643447876s
Interlinking | skos check for Norway fishery stocks dataset took 0.425703763961792s
Timeliness | dataset update frequency check for Norway fishery stocks dataset took 5.91156005859375s
Currency | Creation date check for Norway fishery stocks dataset took 0.5317933559417725s
Currency | Modification date check for Norway fishery stocks dataset took 0.23592853546142578s
Rep.Conc. | URIs length for Norway fishery stocks dataset took 156.61783170700073s
Interoperability | New vocabularies check for Norway fishery stocks dataset took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for Norway fishery stocks dataset took 0.21093177795410156s
Accuracy | Check Functional Property for Norway fishery stocks dataset took 0.2763841152191162s
Accuracy | Check Inverse Functional Property for Norway fishery stocks dataset took 0.35114455223083496s
Accuracy | Check Empty annotation labels for Norway fishery stocks dataset took 44.48140001296997s
Accuracy | Check White space in annotation for Norway fishery stocks dataset took 2.7116966247558594s
Accuracy | Check Datatype consistency for Norway fishery stocks dataset took 2.628523349761963s
Consistency | Disjoint class check for Norway fishery stocks dataset took 0.20923113822937012s
Consistency | Check Misplaced properties for Norway fishery stocks dataset took 82.51798057556152s
Consistency | Misplaced classes for Norway fishery stocks dataset took 8.463330507278442s
Consistency | Check Ontology hijacking for Norway fishery stocks dataset took 39.96980547904968s
Consistency | Check Invalid usage of undefined classes for Norway fishery stocks dataset took 1.3751440048217773s
Consistency | Check Invalid usage of undefined properties for Norway fishery stocks dataset took 83.59193015098572s
Conciseness | Check Extensional conciseness for Norway fishery stocks dataset took 2.7396576404571533s
Conciseness | Check Intensional conciseness for Norway fishery stocks dataset took 0.5168993473052979s
Security | Sign check for Norway fishery stocks dataset took 0.46700119972229004s
Availability | Check URIs Dereferenciability for Norway fishery stocks dataset took 10.761403799057007s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 1.293950080871582s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 4.267692565917969e-05s
Interoperability | Check the re-using of existing vocabs for Norway fishery stocks dataset took 2.1457672119140625e-06s
Believability | Calculation of trust value for Norway fishery stocks dataset took 9.775161743164062e-06s
INFO | --- Analysis for Norway_Fishery_ took 2288.6985149383545s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 0.348771333694458s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0006103515625s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.728316068649292s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020740270614624023s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 5.1975250244140625e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 7.152557373046875e-06s
INFO | --- Analysis for norwegian-geo-divisions took 8.868908882141113s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.100799560546875e-05s
Availability | VoID file availability check for NorwegianSoE took 0.00038170814514160156s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.2796013355255127s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.0994415283203125e-05s
Believability | Calculation of trust value for NorwegianSoE took 7.152557373046875e-06s
INFO | --- Analysis for norwegiansoe took 4.243042230606079s
Availability | SPARQL endpoint availability check for NITP took 4.76837158203125e-05s
Availability | VoID file availability check for NITP took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for NITP took 0.2905588150024414s
Reputation | Calculation of the PageRank for NITP took 0.02065587043762207s
Interlinking | Calculation of Degree of Connection for NITP took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NITP took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for NITP took 6.604194641113281e-05s
Believability | Calculation of trust value for NITP took 6.67572021484375e-06s
INFO | --- Analysis for notIdentifier took 3.11909556388855s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.458427429199219e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.27485156059265137s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007774829864501953s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 4.38690185546875e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 6.67572021484375e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.7869200706481934s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 4.124641418457031e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.2969980239868164s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.7894973754882812e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 7.3909759521484375e-06s
INFO | --- Analysis for npg took 3.433537006378174s
Availability | SPARQL endpoint availability check for NPM took 4.601478576660156e-05s
Availability | VoID file availability check for NPM took 0.0006220340728759766s
Completeness | Calculation of interlinking completeness for NPM took 0.2623732089996338s
Reputation | Calculation of the PageRank for NPM took 0.02074432373046875s
Interlinking | Calculation of Degree of Connection for NPM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NPM took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for NPM took 3.170967102050781e-05s
Believability | Calculation of trust value for NPM took 7.152557373046875e-06s
INFO | --- Analysis for npm took 3.6680338382720947s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.04371786117553711s
Availability | VoID file availability check for NTNU special collections took 0.0006685256958007812s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2680959701538086s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02031540870666504s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.602836608886719e-05s
Believability | Calculation of trust value for NTNU special collections took 7.867813110351562e-06s
INFO | --- Analysis for ntnusc took 5.578647613525391s
Availability | SPARQL endpoint availability check for links took 4.291534423828125e-05s
Availability | VoID file availability check for links took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for links took 0.2515134811401367s
Reputation | Calculation of the PageRank for links took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for links took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for links took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for links took 1.1682510375976562e-05s
Believability | Calculation of trust value for links took 7.3909759521484375e-06s
INFO | --- Analysis for nugmyanmar took 2.4005627632141113s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.482269287109375e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.2752218246459961s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020342588424682617s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.918212890625e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 5.0067901611328125e-06s
INFO | --- Analysis for nuts-geovocab took 2.489839792251587s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 0.4097294807434082s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0006341934204101562s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.2610325813293457s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02117609977722168s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 7.343292236328125e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 6.67572021484375e-06s
INFO | --- Analysis for nvd took 4.110598564147949s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 0.8534336090087891s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.0005934238433837891s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.29915714263916016s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 8.96453857421875e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 7.867813110351562e-06s
INFO | --- Analysis for nvs took 8.422913074493408s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.267692565917969e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.27190566062927246s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.00018405914306640625s
Believability | Calculation of trust value for New York Times - Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.4828038215637207s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 4.172325134277344e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2768831253051758s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.123283386230469e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 6.9141387939453125e-06s
INFO | --- Analysis for o-anc took 2.914029598236084s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.172325134277344e-05s
Availability | VoID file availability check for OANetzwerk took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.2686796188354492s
Reputation | Calculation of the PageRank for OANetzwerk took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 2.86102294921875e-05s
Believability | Calculation of trust value for OANetzwerk took 7.62939453125e-06s
INFO | --- Analysis for oanetzwerk took 2.95625376701355s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 5.173683166503906e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2802143096923828s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.02034616470336914s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 2.8133392333984375e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 1.5497207641601562e-05s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.9712209701538086s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 0.4430999755859375s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.0006999969482421875s
Extra | Recovery of all triples for Italian Chamber of Deputies - official dataset took 1.717785120010376s
Performance | Total latancy measurement for Italian Chamber of Deputies - official dataset took 1.645251989364624s
Amount of data | Number of triples check for Italian Chamber of Deputies - official dataset took 2.636993408203125s
Interoperability | New terms check for Italian Chamber of Deputies - official dataset took 3.8117735385894775s
Versatility | Languages check for Italian Chamber of Deputies - official dataset took 60.28368949890137s
Interpretability | Number of blank nodes check for Italian Chamber of Deputies - official dataset took 2.495380401611328s
Security | Check HTTPS for Italian Chamber of Deputies - official dataset took 0.29725170135498047s
Interpretability | RDF structures check for Italian Chamber of Deputies - official dataset took 0.41339612007141113s
Versatility | Serialization formats check for Italian Chamber of Deputies - official dataset took 0.5635077953338623s
Availability | RDF dump link check for Italian Chamber of Deputies - official dataset took 0.40535712242126465s
License | MR license check for Italian Chamber of Deputies - official dataset took 0.38312792778015137s
License | HR license check for Italian Chamber of Deputies - official dataset took 60.37027955055237s
Amount of data | Number of property check for Italian Chamber of Deputies - official dataset took 0.30884814262390137s
Understandability | Number of label check for Italian Chamber of Deputies - official dataset took 0.7863197326660156s
Understandability | URI regex check for Italian Chamber of Deputies - official dataset took 0.6961381435394287s
Understandability | Vocabs check for Italian Chamber of Deputies - official dataset took 0.5456805229187012s
Verifiability | Authors check for Italian Chamber of Deputies - official dataset took 0.33290791511535645s
Verifiability | Publishers check for Italian Chamber of Deputies - official dataset took 0.3421785831451416s
Performance | Throughput check for Italian Chamber of Deputies - official dataset took 12.751120328903198s
Amount of data | Check the number of entities for Italian Chamber of Deputies - official dataset took 7.557868957519531e-05s
Verifiability | Contribs. check for Italian Chamber of Deputies - official dataset took 0.4491848945617676s
Interlinking | sameAs chians check for Italian Chamber of Deputies - official dataset took 0.36849355697631836s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.37959837913513184s
Interlinking | skos check for Italian Chamber of Deputies - official dataset took 0.33696913719177246s
Timeliness | dataset update frequency check for Italian Chamber of Deputies - official dataset took 1.6711781024932861s
Currency | Creation date check for Italian Chamber of Deputies - official dataset took 0.6777863502502441s
Currency | Modification date check for Italian Chamber of Deputies - official dataset took 0.32741355895996094s
Rep.Conc. | URIs length for Italian Chamber of Deputies - official dataset took 17.86121106147766s
Interoperability | New vocabularies check for Italian Chamber of Deputies - official dataset took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for Italian Chamber of Deputies - official dataset took 0.37807440757751465s
Accuracy | Check Functional Property for Italian Chamber of Deputies - official dataset took 1.0599629878997803s
Accuracy | Check Inverse Functional Property for Italian Chamber of Deputies - official dataset took 0.40453076362609863s
Accuracy | Check Empty annotation labels for Italian Chamber of Deputies - official dataset took 1.076026201248169s
Accuracy | Check White space in annotation for Italian Chamber of Deputies - official dataset took 0.023929834365844727s
Accuracy | Check Datatype consistency for Italian Chamber of Deputies - official dataset took 0.02872443199157715s
Consistency | Disjoint class check for Italian Chamber of Deputies - official dataset took 0.32176756858825684s
Consistency | Check Misplaced properties for Italian Chamber of Deputies - official dataset took 13.414044618606567s
Consistency | Misplaced classes for Italian Chamber of Deputies - official dataset took 0.5949718952178955s
Consistency | Check Ontology hijacking for Italian Chamber of Deputies - official dataset took 3.5952727794647217s
Consistency | Check Invalid usage of undefined classes for Italian Chamber of Deputies - official dataset took 1.3106906414031982s
Consistency | Check Invalid usage of undefined properties for Italian Chamber of Deputies - official dataset took 14.333053350448608s
Conciseness | Check Extensional conciseness for Italian Chamber of Deputies - official dataset took 0.03174161911010742s
Conciseness | Check Intensional conciseness for Italian Chamber of Deputies - official dataset took 0.3429281711578369s
Security | Sign check for Italian Chamber of Deputies - official dataset took 0.3192903995513916s
Availability | Check URIs Dereferenciability for Italian Chamber of Deputies - official dataset took 10.699913263320923s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.3340761661529541s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.021173954010009766s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 2.3126602172851562e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0008220672607421875s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 0.00011181831359863281s
Interoperability | Check the re-using of existing vocabs for Italian Chamber of Deputies - official dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 7.867813110351562e-06s
INFO | --- Analysis for ocd took 434.2380862236023s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 5.245208740234375e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0007195472717285156s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.6881828308105469s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020722389221191406s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 4.792213439941406e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 3.62396240234375e-05s
INFO | --- Analysis for oceandrilling-borehole took 3.62917160987854s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 1.382321834564209s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0008029937744140625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.2784121036529541s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020911693572998047s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.320808410644531e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 7.3909759521484375e-06s
INFO | --- Analysis for oceandrilling-codices took 7.6819446086883545s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 1.2081983089447021s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.27696657180786133s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.022309303283691406s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0011522769927978516s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 4.1484832763671875e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 5.607228517532349s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 1.2170193195343018s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.27448415756225586s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-forams took 5.819716691970825s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 1.264106273651123s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0007510185241699219s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.28298258781433105s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020601511001586914s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007565021514892578s
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 8.821487426757812e-06s
INFO | --- Analysis for oceandrilling-janus took 5.89455509185791s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 11.042621374130249s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0007612705230712891s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.2886497974395752s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 6.9141387939453125e-06s
INFO | --- Analysis for oceandrilling-janusamp took 15.641063213348389s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1770334243774414s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007259845733642578s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.25527334213256836s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-ldeo took 5.933929443359375s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.3392181396484375e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0007214546203613281s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.28435564041137695s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.02305293083190918s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.001009225845336914s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 6.985664367675781e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 7.867813110351562e-06s
INFO | --- Analysis for oclc-fast took 10.776899814605713s
Availability | SPARQL endpoint availability check for Open Data Communities took 5.435943603515625e-05s
Availability | VoID file availability check for Open Data Communities took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.27463507652282715s
Reputation | Calculation of the PageRank for Open Data Communities took 0.022958993911743164s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0010161399841308594s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.409385681152344e-05s
Believability | Calculation of trust value for Open Data Communities took 7.62939453125e-06s
INFO | --- Analysis for odc took 2.9033639430999756s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.59130859375s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.26879024505615234s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020367860794067383s
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.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.0279159545898438e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 5.245208740234375e-06s
INFO | --- Analysis for odc-imd-environment-score took 5.00750207901001s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.076957702636719e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.2728409767150879s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020389080047607422s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.765655517578125e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 1.5974044799804688e-05s
INFO | --- Analysis for odc-imd-rank-2007 took 2.9970908164978027s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 0.739389181137085s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.7580339908599854s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.7126109600067139s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.838539123535156e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 4.76837158203125e-06s
INFO | --- Analysis for odc-lsoa took 7.258605241775513s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 4.267692565917969e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.23878812789916992s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.022455453872680664s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0009801387786865234s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.409385681152344e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 1.2159347534179688e-05s
INFO | --- Analysis for odc-population-2005 took 2.92643404006958s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.1484832763671875e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.29250597953796387s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.86102294921875e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 7.152557373046875e-06s
INFO | --- Analysis for ods took 3.0083255767822266s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.4188730716705322s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.28478360176086426s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.021207809448242188s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0010120868682861328s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.00011157989501953125s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for oecd-linked-data took 2.899279832839966s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.076957702636719e-05s
Availability | VoID file availability check for Offener Haushalt took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.2860426902770996s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020270109176635742s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007452964782714844s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.7418136596679688e-05s
Believability | Calculation of trust value for Offener Haushalt took 7.62939453125e-06s
INFO | --- Analysis for offener-haushalt took 3.0030007362365723s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 30.354851007461548s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.0006353855133056641s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2752974033355713s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020406007766723633s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.029273986816406e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 6.9141387939453125e-06s
INFO | --- Analysis for ogolod took 102.93349599838257s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.315376281738281e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0006318092346191406s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.6771631240844727s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020257234573364258s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.315376281738281e-05s
Believability | Calculation of trust value for OLAC Metadata took 6.9141387939453125e-06s
INFO | --- Analysis for olac took 23.442142009735107s
Availability | SPARQL endpoint availability check for OLiA took 4.220008850097656e-05s
Availability | VoID file availability check for OLiA took 0.0007481575012207031s
Completeness | Calculation of interlinking completeness for OLiA took 0.26654529571533203s
Reputation | Calculation of the PageRank for OLiA took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for OLiA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00012183189392089844s
Believability | Calculation of trust value for OLiA took 6.67572021484375e-06s
INFO | --- Analysis for olia took 12.652119398117065s
Availability | SPARQL endpoint availability check for OLiA Discourse took 4.315376281738281e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0008296966552734375s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.27742648124694824s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.743171691894531e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.33514404296875e-05s
INFO | --- Analysis for olia-discourse took 7.25770115852356s
Availability | SPARQL endpoint availability check for Open Land Use took 0.283613920211792s
Availability | VoID file availability check for Open Land Use took 0.000347137451171875s
Extra | Recovery of all triples for Open Land Use took 120.8528904914856s
Performance | Total latancy measurement for Open Land Use took 0.9611742496490479s
Amount of data | Number of triples check for Open Land Use took 8.057085514068604s
Interoperability | New terms check for Open Land Use took 13.587143421173096s
Versatility | Languages check for Open Land Use took 300.194628238678s
Interpretability | Number of blank nodes check for Open Land Use took 3.1395039558410645s
Interpretability | RDF structures check for Open Land Use took 0.23459672927856445s
Versatility | Serialization formats check for Open Land Use took 9.745388746261597s
Availability | RDF dump link check for Open Land Use took 0.2963552474975586s
License | MR license check for Open Land Use took 0.607703685760498s
License | HR license check for Open Land Use took 300.154935836792s
Amount of data | Number of property check for Open Land Use took 0.31080031394958496s
Understandability | Number of label check for Open Land Use took 2.9314963817596436s
Understandability | URI regex check for Open Land Use took 0.7457942962646484s
Understandability | Vocabs check for Open Land Use took 0.45156049728393555s
Verifiability | Authors check for Open Land Use took 0.20010590553283691s
Verifiability | Publishers check for Open Land Use took 0.2790257930755615s
Performance | Throughput check for Open Land Use took 10.900243282318115s
Amount of data | Check the number of entities for Open Land Use took 7.62939453125e-05s
Verifiability | Contribs. check for Open Land Use took 0.19835472106933594s
Interlinking | sameAs chians check for Open Land Use took 0.1734633445739746s
Interlinking | skos check for Open Land Use took 0.43689465522766113s
Interlinking | skos check for Open Land Use took 0.463381290435791s
Timeliness | dataset update frequency check for Open Land Use took 5.64382266998291s
Currency | Creation date check for Open Land Use took 0.47849273681640625s
Currency | Modification date check for Open Land Use took 0.22220206260681152s
Rep.Conc. | URIs length for Open Land Use took 153.64872431755066s
Interoperability | New vocabularies check for Open Land Use took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use took 0.2139720916748047s
Accuracy | Check Functional Property for Open Land Use took 0.33635735511779785s
Accuracy | Check Inverse Functional Property for Open Land Use took 0.3681313991546631s
Accuracy | Check Empty annotation labels for Open Land Use took 37.35984683036804s
Accuracy | Check White space in annotation for Open Land Use took 2.6612846851348877s
Accuracy | Check Datatype consistency for Open Land Use took 2.59808349609375s
Consistency | Disjoint class check for Open Land Use took 0.19620180130004883s
Consistency | Check Misplaced properties for Open Land Use took 81.0711669921875s
Consistency | Misplaced classes for Open Land Use took 8.512511968612671s
Consistency | Check Ontology hijacking for Open Land Use took 37.26378607749939s
Consistency | Check Invalid usage of undefined classes for Open Land Use took 1.4250328540802002s
Consistency | Check Invalid usage of undefined properties for Open Land Use took 83.07000970840454s
Conciseness | Check Extensional conciseness for Open Land Use took 2.7829363346099854s
Conciseness | Check Intensional conciseness for Open Land Use took 0.5583834648132324s
Security | Sign check for Open Land Use took 0.7675278186798096s
Availability | Check URIs Dereferenciability for Open Land Use took 9.997737407684326s
Completeness | Calculation of interlinking completeness for Open Land Use took 1.6178960800170898s
Reputation | Calculation of the PageRank for Open Land Use took 0.021045207977294922s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use took 3.337860107421875e-06s
Believability | Calculation of trust value for Open Land Use took 7.152557373046875e-06s
INFO | --- Analysis for OLU took 2252.2500030994415s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.2438507080078125e-05s
Availability | VoID file availability check for OmegaWiki took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.7098629474639893s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.7670135498046875e-05s
Believability | Calculation of trust value for OmegaWiki took 1.239776611328125e-05s
INFO | --- Analysis for omegawiki took 4.75680685043335s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.6453254222869873s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2854161262512207s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.026863813400268555s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0013048648834228516s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 4.863739013671875e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-als took 5.537982225418091s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.26844310760498047s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.2676272392272949s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-arb took 3.5188372135162354s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.22154855728149414s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.6802489757537842s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-bul took 3.734555721282959s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.22206354141235352s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.000835418701171875s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.754549503326416s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-cow took 3.4924986362457275s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2126450538635254s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00037670135498046875s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2854161262512207s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020245075225830078s
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.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-cwn took 2.970987319946289s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.18160343170166016s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0006878376007080078s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.26325297355651855s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020459651947021484s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-dan took 3.3440792560577393s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.18654870986938477s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0006818771362304688s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2704343795776367s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.021834611892700195s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0009183883666992188s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-ell took 2.9127676486968994s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.2166306972503662s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0010652542114257812s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.27604126930236816s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.02028822898864746s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-eng took 2.904524326324463s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.19231843948364258s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.27791738510131836s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020505905151367188s
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.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-fas took 3.0174453258514404s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.19533944129943848s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.2741973400115967s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02070784568786621s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-fin took 2.8843512535095215s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.19538640975952148s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.2568376064300537s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020295381546020508s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-fra took 2.8335609436035156s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.20352387428283691s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.2701904773712158s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.000762939453125s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-heb took 2.882246255874634s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.21579265594482422s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0003581047058105469s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.2814662456512451s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02049541473388672s
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.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.695487976074219e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-hrv took 2.915771722793579s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.18492507934570312s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2611427307128906s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020503759384155273s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-isl took 2.8508896827697754s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.20112967491149902s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.3005228042602539s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.02109503746032715s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007669925689697266s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
INFO | --- Analysis for omwn-ita took 2.927495002746582s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.19135427474975586s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.24642682075500488s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-iwn took 2.858813524246216s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.21320843696594238s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.000370025634765625s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2531130313873291s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-jpn took 2.899207353591919s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.22505760192871094s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.29069089889526367s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 2.1696090698242188e-05s
INFO | --- Analysis for omwn-mcr took 2.984957456588745s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.21972441673278809s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.25806713104248047s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-msa took 2.918297052383423s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.2081286907196045s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.2701098918914795s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-nld took 2.9220147132873535s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.18699359893798828s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.27388882637023926s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.021118640899658203s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.838539123535156e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-nor took 2.9121577739715576s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.20049548149108887s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.25542545318603516s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020450592041015625s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007526874542236328s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.337860107421875e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
INFO | --- Analysis for omwn-pol took 2.889259099960327s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.1961805820465088s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2583930492401123s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02052927017211914s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-por took 2.9223124980926514s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.18231868743896484s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.2563347816467285s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0008554458618164062s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ron took 2.9259631633758545s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.19398784637451172s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2607901096343994s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 4.363059997558594e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-slk took 2.879608154296875s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.19999337196350098s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.25695252418518066s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.020864486694335938s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0009796619415283203s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.291534423828125e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-slv took 2.9146430492401123s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2091670036315918s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.2752041816711426s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-swe took 3.024732828140259s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.1877002716064453s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0005183219909667969s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.28136110305786133s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.000843048095703125s
Interlinking | Calculation of Clustering coefficient for Thai WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 6.67572021484375e-06s
INFO | --- Analysis for omwn-tha took 2.9085919857025146s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 8.669424533843994s
Availability | VoID file availability check for OntoBeef Domain took 0.0006358623504638672s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2516970634460449s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020163297653198242s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.0531158447265625e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.152557373046875e-06s
INFO | --- Analysis for ontobeef-domain took 36.4092173576355s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.1961669921875e-05s
Availability | VoID file availability check for Ontos News Portal took 0.0005688667297363281s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.2732212543487549s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.020348548889160156s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 8.7738037109375e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.152557373046875e-06s
INFO | --- Analysis for ontos-news-portal took 5.302959680557251s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 5.6743621826171875e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2791788578033447s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.218650817871094e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.3909759521484375e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.5371406078338623s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.267692565917969e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.000701904296875s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.2971024513244629s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02037191390991211s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.5762786865234375e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.4373016357421875e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 10.360454082489014s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.0531158447265625e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2780015468597412s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.8371810913085938e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.934141159057617s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.267692565917969e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0005519390106201172s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2666149139404297s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.553794860839844e-05s
Believability | Calculation of trust value for Open Data Euskadi took 5.245208740234375e-06s
INFO | --- Analysis for open-data-euskadi took 8.225252628326416s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 4.291534423828125e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.2780270576477051s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020212173461914062s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010156631469726562s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.3909759521484375e-06s
INFO | --- Analysis for open-data-risp took 6.83630895614624s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 0.2542085647583008s
Availability | VoID file availability check for Open Data Thesaurus took 0.0004050731658935547s
Extra | Recovery of all triples for Open Data Thesaurus took 1.623868703842163s
Performance | Total latancy measurement for Open Data Thesaurus took 0.5067434310913086s
Amount of data | Number of triples check for Open Data Thesaurus took 0.10248136520385742s
Interoperability | New terms check for Open Data Thesaurus took 1.3937485218048096s
Versatility | Languages check for Open Data Thesaurus took 0.11852884292602539s
Interpretability | Number of blank nodes check for Open Data Thesaurus took 0.12904834747314453s
Security | Check HTTPS for Open Data Thesaurus took 0.3344273567199707s
Interpretability | RDF structures check for Open Data Thesaurus took 0.12022161483764648s
Versatility | Serialization formats check for Open Data Thesaurus took 0.12214159965515137s
Availability | RDF dump link check for Open Data Thesaurus took 1.1490421295166016s
License | MR license check for Open Data Thesaurus took 0.12717723846435547s
License | HR license check for Open Data Thesaurus took 0.11266493797302246s
Amount of data | Number of property check for Open Data Thesaurus took 0.12730813026428223s
Understandability | Number of label check for Open Data Thesaurus took 0.11234927177429199s
Understandability | URI regex check for Open Data Thesaurus took 0.17714691162109375s
Understandability | Vocabs check for Open Data Thesaurus took 0.14406156539916992s
Verifiability | Authors check for Open Data Thesaurus took 0.12808537483215332s
Verifiability | Publishers check for Open Data Thesaurus took 0.10239648818969727s
Performance | Throughput check for Open Data Thesaurus took 10.579140424728394s
Amount of data | Check the number of entities for Open Data Thesaurus took 4.9591064453125e-05s
Verifiability | Contribs. check for Open Data Thesaurus took 0.12562346458435059s
Interlinking | sameAs chians check for Open Data Thesaurus took 0.13891386985778809s
Interlinking | skos check for Open Data Thesaurus took 0.14195966720581055s
Interlinking | skos check for Open Data Thesaurus took 0.10192394256591797s
Timeliness | dataset update frequency check for Open Data Thesaurus took 0.09290504455566406s
Currency | Creation date check for Open Data Thesaurus took 0.21800518035888672s
Currency | Modification date check for Open Data Thesaurus took 0.20579195022583008s
Rep.Conc. | URIs length for Open Data Thesaurus took 0.43672990798950195s
Interoperability | New vocabularies check for Open Data Thesaurus took 3.6980984210968018s
Consistency | Deprecated classes/propertiers check for Open Data Thesaurus took 0.1397714614868164s
Accuracy | Check Functional Property for Open Data Thesaurus took 0.08806324005126953s
Accuracy | Check Inverse Functional Property for Open Data Thesaurus took 0.09350180625915527s
Accuracy | Check Empty annotation labels for Open Data Thesaurus took 0.2093033790588379s
Accuracy | Check White space in annotation for Open Data Thesaurus took 0.001140594482421875s
Consistency | Disjoint class check for Open Data Thesaurus took 0.07987070083618164s
Consistency | Check Misplaced properties for Open Data Thesaurus took 0.19665217399597168s
Consistency | Misplaced classes for Open Data Thesaurus took 0.09182262420654297s
Consistency | Check Ontology hijacking for Open Data Thesaurus took 1.437997579574585s
Consistency | Check Invalid usage of undefined properties for Open Data Thesaurus took 1.3808131217956543s
Conciseness | Check Extensional conciseness for Open Data Thesaurus took 0.0001361370086669922s
Security | Sign check for Open Data Thesaurus took 0.07825207710266113s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.27648162841796875s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.019998788833618164s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 8.416175842285156e-05s
Interoperability | Check the re-using of existing vocabs for Open Data Thesaurus took 2.651183605194092s
Believability | Calculation of trust value for Open Data Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for open-data-thesaurus took 115.02265501022339s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.5299530029296875e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0005438327789306641s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.2753174304962158s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0007140636444091797s
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 7.152557373046875e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.981107711791992s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.410743713378906e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.25054216384887695s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.0204312801361084s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.651878356933594e-05s
Believability | Calculation of trust value for Open Election Data Project took 5.0067901611328125e-06s
INFO | --- Analysis for open-election-data-project took 2.4584574699401855s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 4.192654371261597s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.24771451950073242s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.606910705566406e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 4.76837158203125e-06s
INFO | --- Analysis for open-energy-info-wiki took 10.91830062866211s
Availability | SPARQL endpoint availability check for Open Library took 4.291534423828125e-05s
Availability | VoID file availability check for Open Library took 0.000370025634765625s
Completeness | Calculation of interlinking completeness for Open Library took 0.2502906322479248s
Reputation | Calculation of the PageRank for Open Library took 0.020595073699951172s
Interlinking | Calculation of Degree of Connection for Open Library took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Library took 0.0007863044738769531s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.842613220214844e-05s
Believability | Calculation of trust value for Open Library took 7.3909759521484375e-06s
INFO | --- Analysis for open-library took 26.385599613189697s
Availability | SPARQL endpoint availability check for Open Directory took 4.076957702636719e-05s
Availability | VoID file availability check for Open Directory took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for Open Directory took 0.28655266761779785s
Reputation | Calculation of the PageRank for Open Directory took 0.020184755325317383s
Interlinking | Calculation of Degree of Connection for Open Directory took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open Directory took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Open Directory took 2.765655517578125e-05s
Believability | Calculation of trust value for Open Directory took 7.867813110351562e-06s
INFO | --- Analysis for open_directory took 2.934260606765747s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 0.18734073638916016s
Availability | VoID file availability check for Open Land Use @PSNC took 0.00024318695068359375s
Extra | Recovery of all triples for Open Land Use @PSNC took 117.17221069335938s
Performance | Total latancy measurement for Open Land Use @PSNC took 0.9973490238189697s
Amount of data | Number of triples check for Open Land Use @PSNC took 8.324522018432617s
Interoperability | New terms check for Open Land Use @PSNC took 13.865318536758423s
Versatility | Languages check for Open Land Use @PSNC took 300.2118966579437s
Interpretability | Number of blank nodes check for Open Land Use @PSNC took 2.7674951553344727s
Interpretability | RDF structures check for Open Land Use @PSNC took 0.26357364654541016s
Versatility | Serialization formats check for Open Land Use @PSNC took 12.298969507217407s
Availability | RDF dump link check for Open Land Use @PSNC took 0.29717087745666504s
License | MR license check for Open Land Use @PSNC took 0.5772416591644287s
License | HR license check for Open Land Use @PSNC took 300.22055196762085s
Amount of data | Number of property check for Open Land Use @PSNC took 0.20355987548828125s
Understandability | Number of label check for Open Land Use @PSNC took 2.5052003860473633s
Understandability | URI regex check for Open Land Use @PSNC took 0.6022853851318359s
Understandability | Vocabs check for Open Land Use @PSNC took 0.4736778736114502s
Verifiability | Authors check for Open Land Use @PSNC took 0.20111393928527832s
Verifiability | Publishers check for Open Land Use @PSNC took 0.23977923393249512s
Performance | Throughput check for Open Land Use @PSNC took 11.615132331848145s
Amount of data | Check the number of entities for Open Land Use @PSNC took 0.00010156631469726562s
Verifiability | Contribs. check for Open Land Use @PSNC took 0.19585227966308594s
Interlinking | sameAs chians check for Open Land Use @PSNC took 0.17911314964294434s
Interlinking | skos check for Open Land Use @PSNC took 0.45490241050720215s
Interlinking | skos check for Open Land Use @PSNC took 0.46714043617248535s
Timeliness | dataset update frequency check for Open Land Use @PSNC took 7.57017183303833s
Currency | Creation date check for Open Land Use @PSNC took 0.48151493072509766s
Currency | Modification date check for Open Land Use @PSNC took 0.22294306755065918s
Rep.Conc. | URIs length for Open Land Use @PSNC took 154.34470319747925s
Interoperability | New vocabularies check for Open Land Use @PSNC took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for Open Land Use @PSNC took 0.1991443634033203s
Accuracy | Check Functional Property for Open Land Use @PSNC took 0.2532002925872803s
Accuracy | Check Inverse Functional Property for Open Land Use @PSNC took 0.3602914810180664s
Accuracy | Check Empty annotation labels for Open Land Use @PSNC took 42.18496823310852s
Accuracy | Check White space in annotation for Open Land Use @PSNC took 2.667659282684326s
Accuracy | Check Datatype consistency for Open Land Use @PSNC took 2.568941354751587s
Consistency | Disjoint class check for Open Land Use @PSNC took 0.19994211196899414s
Consistency | Check Misplaced properties for Open Land Use @PSNC took 84.45948886871338s
Consistency | Misplaced classes for Open Land Use @PSNC took 8.967941761016846s
Consistency | Check Ontology hijacking for Open Land Use @PSNC took 35.260327100753784s
Consistency | Check Invalid usage of undefined classes for Open Land Use @PSNC took 1.3728485107421875s
Consistency | Check Invalid usage of undefined properties for Open Land Use @PSNC took 81.48581719398499s
Conciseness | Check Extensional conciseness for Open Land Use @PSNC took 2.759503126144409s
Conciseness | Check Intensional conciseness for Open Land Use @PSNC took 0.601815938949585s
Security | Sign check for Open Land Use @PSNC took 0.7867777347564697s
Availability | Check URIs Dereferenciability for Open Land Use @PSNC took 9.871078729629517s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.9816980361938477s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.021017789840698242s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 4.1961669921875e-05s
Interoperability | Check the re-using of existing vocabs for Open Land Use @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Open_Land_Use took 2261.8732545375824s
Availability | SPARQL endpoint availability check for flyatlas took 1.7177493572235107s
Availability | VoID file availability check for flyatlas took 0.00033545494079589844s
Completeness | Calculation of interlinking completeness for flyatlas took 0.24063420295715332s
Reputation | Calculation of the PageRank for flyatlas took 0.021245718002319336s
Interlinking | Calculation of Degree of Connection for flyatlas took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for flyatlas took 0.0009534358978271484s
Interlinking | Calculation of Clustering coefficient for flyatlas took 3.4809112548828125e-05s
Believability | Calculation of trust value for flyatlas took 6.67572021484375e-06s
INFO | --- Analysis for openbiomed-flyatlas took 9.960235357284546s
Availability | SPARQL endpoint availability check for OpenCalais took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenCalais took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.25903773307800293s
Reputation | Calculation of the PageRank for OpenCalais took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010848045349121094s
Believability | Calculation of trust value for OpenCalais took 6.67572021484375e-06s
INFO | --- Analysis for opencalais took 7.097048282623291s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 4.649162292480469e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.25717997550964355s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020624160766601562s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.52587890625e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.772445678710938e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 5.0067901611328125e-06s
INFO | --- Analysis for opencorporates took 4.293212175369263s
Availability | SPARQL endpoint availability check for OpenCyc took 5.221366882324219e-05s
Availability | VoID file availability check for OpenCyc took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.24458098411560059s
Reputation | Calculation of the PageRank for OpenCyc took 0.02027440071105957s
Interlinking | Calculation of Degree of Connection for OpenCyc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenCyc took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.0001049041748046875s
Believability | Calculation of trust value for OpenCyc took 6.9141387939453125e-06s
INFO | --- Analysis for opencyc took 2.7538530826568604s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 8.0108642578125e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.24961137771606445s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.504753112792969e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 4.155909061431885s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.0010576248168945312s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.2643861770629883s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02114272117614746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0008335113525390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 3.114071846008301s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.2950592041015625s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.0422961711883545s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.00037479400634765625s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.27286648750305176s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.4007365703582764s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 0.00012063980102539062s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.28551602363586426s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 3.2091305255889893s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.241424560546875s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.8802568912506104s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 5.245208740234375e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0007066726684570312s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.28385043144226074s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 5.0067901611328125e-06s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.9650321006774902s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.263624906539917s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.4050533771514893s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0014605522155761719s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.26268434524536133s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.1207332611083984s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0006527900695800781s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.254849910736084s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 0.0031652450561523438s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 3.0605900287628174s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 5.14984130859375e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0006389617919921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.2523972988128662s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020771503448486328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.673004150390625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.910928726196289s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 6.4849853515625e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.26136136054992676s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020531177520751953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.7236406803131104s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.00074005126953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.28571438789367676s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.922304391860962s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.2485353946685791s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020742416381835938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.3166933059692383s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0005974769592285156s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.2685525417327881s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.9882497787475586s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 5.817413330078125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.2734034061431885s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.857372999191284s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 7.748603820800781e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.2656588554382324s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.943182945251465s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.863739013671875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.0005524158477783203s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.2733278274536133s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020685911178588867s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 5.4836273193359375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.874455451965332s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.24965429306030273s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 5.245208740234375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.3092405796051025s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.673004150390625e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007419586181640625s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.27001404762268066s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0007231235504150391s
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 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.909860849380493s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0007166862487792969s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.27193641662597656s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.021655559539794922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 3.050849199295044s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0006635189056396484s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.2651069164276123s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 3.023205041885376s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0006041526794433594s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.2550172805786133s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.8955438137054443s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0008106231689453125s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2611210346221924s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.021249055862426758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0011875629425048828s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 5.91278076171875e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.8437933921813965s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.458427429199219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0006968975067138672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.2544097900390625s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020749568939208984s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.315376281738281e-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 3.127215623855591s
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.0006492137908935547s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.2842104434967041s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02079033851623535s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.6226043701171875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.482269287109375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.9444453716278076s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0006392002105712891s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.24821949005126953s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.855769395828247s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007102489471435547s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.2622811794281006s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.031745672225952s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.363059997558594e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.2860391139984131s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.8160552978515625e-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 3.0894229412078857s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 5.8650970458984375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.2639470100402832s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020601987838745117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 3.012455701828003s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.00038504600524902344s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.28286099433898926s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.0534579753875732s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007462501525878906s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2903578281402588s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020673036575317383s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.4345855712890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.9892756938934326s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007274150848388672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2897670269012451s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020633697509765625s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.6253204345703125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.936394214630127s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.00032591819763183594s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.2388896942138672s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020498037338256836s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.3401741981506348s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2680671215057373s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.4137234687805176s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006880760192871094s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2761099338531494s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.97202730178833s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.38690185546875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007803440093994141s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.2668898105621338s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020412206649780273s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 3.014155387878418s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.482269287109375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007765293121337891s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.28388428688049316s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.021427631378173828s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.76837158203125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.9838829040527344s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0006802082061767578s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2716953754425049s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.8781354427337646s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.649162292480469e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0012714862823486328s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.2659175395965576s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020417213439941406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.649162292480469e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.958862543106079s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0005843639373779297s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.259873628616333s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.0126140117645264s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 9.012222290039062e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.28056836128234863s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.600120544433594e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.8718509674072266s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.3392181396484375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.269726037979126s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02036428451538086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.8005337715148926s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 6.382267236709595s
Availability | VoID file availability check for Open Data of Ecuador took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.2734065055847168s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 0.00010466575622558594s
Believability | Calculation of trust value for Open Data of Ecuador took 8.106231689453125e-06s
INFO | --- Analysis for opendataec took 12.077815294265747s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.291534423828125e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.2558269500732422s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.202629804611206s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.0006465911865234375s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2575187683105469s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 3.1517248153686523s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 4.38690185546875e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.28219103813171387s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.02080535888671875s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.802805185317993s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.2579989433288574s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 6.9141387939453125e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.7576751708984375s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 8.249282836914062e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.27316713333129883s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 7.867813110351562e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.7548270225524902s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.363059997558594e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.26325511932373047s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020337820053100586s
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.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.798031806945801s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.506111145019531e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.26909303665161133s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020711421966552734s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.7382853031158447s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.553794860839844e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.265824556350708s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020526409149169922s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.725393772125244s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.458427429199219e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.2675302028656006s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.02076435089111328s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0009915828704833984s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.3628642559051514s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 30.386195421218872s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.26223182678222656s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 2.7418136596679688e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 7.152557373046875e-06s
INFO | --- Analysis for openlink-lod-cache took 62.82905316352844s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.696846008300781e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.2885279655456543s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.369850158691406e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 8.106231689453125e-06s
INFO | --- Analysis for openlinksw-dataspaces took 2.5009074211120605s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.482269287109375e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.2609133720397949s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.02049708366394043s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0008220672607421875s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.369850158691406e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 5.0067901611328125e-06s
INFO | --- Analysis for openlylocal took 6.068074464797974s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 1.030472993850708s
Availability | VoID file availability check for OpenMobileNetwork took 0.0005712509155273438s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.2570977210998535s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.414817810058594e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 6.4373016357421875e-06s
INFO | --- Analysis for openmobilenetwork took 3.901935338973999s
Availability | SPARQL endpoint availability check for OpenTox took 4.172325134277344e-05s
Availability | VoID file availability check for OpenTox took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for OpenTox took 0.25881361961364746s
Reputation | Calculation of the PageRank for OpenTox took 0.020397663116455078s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for OpenTox took 2.8848648071289062e-05s
Believability | Calculation of trust value for OpenTox took 7.152557373046875e-06s
INFO | --- Analysis for opentox took 3.058771848678589s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.029273986816406e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.286146879196167s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.7418136596679688e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.152557373046875e-06s
INFO | --- Analysis for openuplabs took 2.9564731121063232s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.124641418457031e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.27073168754577637s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.02129983901977539s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007765293121337891s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 2.9087066650390625e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 6.4373016357421875e-06s
INFO | --- Analysis for opus took 2.9467475414276123s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 5.078315734863281e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0003075599670410156s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.2568550109863281s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020576000213623047s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.552436828613281e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.867813110351562e-06s
INFO | --- Analysis for orcid took 2.872483968734741s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 1.0126690864562988s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.26234984397888184s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02254319190979004s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0008878707885742188s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 0.0001049041748046875s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 5.522714614868164s
Availability | SPARQL endpoint availability check for oreilly took 4.1961669921875e-05s
Availability | VoID file availability check for oreilly took 0.000518798828125s
Completeness | Calculation of interlinking completeness for oreilly took 0.26099395751953125s
Reputation | Calculation of the PageRank for oreilly took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for oreilly took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for oreilly took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.57763671875e-05s
Believability | Calculation of trust value for oreilly took 6.9141387939453125e-06s
INFO | --- Analysis for oreilly took 3.8850045204162598s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 3.3851537704467773s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.2703227996826172s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.170967102050781e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 7.152557373046875e-06s
INFO | --- Analysis for Organchem-Data took 7.402480125427246s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 0.056795358657836914s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2979917526245117s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020273447036743164s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.628036499023438e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for organic-edunet took 9.361924648284912s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 0.44927096366882324s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0006959438323974609s
Extra | Recovery of all triples for Open Research Knowledge Graph (ORKG) took 13.52838945388794s
Performance | Total latancy measurement for Open Research Knowledge Graph (ORKG) took 0.7973432540893555s
Amount of data | Number of triples check for Open Research Knowledge Graph (ORKG) took 0.16495561599731445s
Interoperability | New terms check for Open Research Knowledge Graph (ORKG) took 1.6371839046478271s
Versatility | Languages check for Open Research Knowledge Graph (ORKG) took 7.150487184524536s
Interpretability | Number of blank nodes check for Open Research Knowledge Graph (ORKG) took 0.14750075340270996s
Interpretability | RDF structures check for Open Research Knowledge Graph (ORKG) took 0.15130925178527832s
Versatility | Serialization formats check for Open Research Knowledge Graph (ORKG) took 0.1576857566833496s
Availability | RDF dump link check for Open Research Knowledge Graph (ORKG) took 0.1404881477355957s
License | MR license check for Open Research Knowledge Graph (ORKG) took 0.16643881797790527s
License | HR license check for Open Research Knowledge Graph (ORKG) took 4.216708183288574s
Amount of data | Number of property check for Open Research Knowledge Graph (ORKG) took 0.15846943855285645s
Understandability | Number of label check for Open Research Knowledge Graph (ORKG) took 0.2129192352294922s
Understandability | URI regex check for Open Research Knowledge Graph (ORKG) took 0.31359124183654785s
Understandability | Vocabs check for Open Research Knowledge Graph (ORKG) took 0.15547513961791992s
Verifiability | Authors check for Open Research Knowledge Graph (ORKG) took 0.15812277793884277s
Verifiability | Publishers check for Open Research Knowledge Graph (ORKG) took 0.16771435737609863s
Performance | Throughput check for Open Research Knowledge Graph (ORKG) took 10.760014772415161s
Amount of data | Check the number of entities for Open Research Knowledge Graph (ORKG) took 0.0001347064971923828s
Verifiability | Contribs. check for Open Research Knowledge Graph (ORKG) took 0.14530229568481445s
Interlinking | sameAs chians check for Open Research Knowledge Graph (ORKG) took 0.1237649917602539s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.18038368225097656s
Interlinking | skos check for Open Research Knowledge Graph (ORKG) took 0.1755387783050537s
Timeliness | dataset update frequency check for Open Research Knowledge Graph (ORKG) took 0.21256422996520996s
Currency | Creation date check for Open Research Knowledge Graph (ORKG) took 0.40183210372924805s
Currency | Modification date check for Open Research Knowledge Graph (ORKG) took 0.4721372127532959s
Rep.Conc. | URIs length for Open Research Knowledge Graph (ORKG) took 7.251964092254639s
Interoperability | New vocabularies check for Open Research Knowledge Graph (ORKG) took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for Open Research Knowledge Graph (ORKG) took 0.13021206855773926s
Accuracy | Check Functional Property for Open Research Knowledge Graph (ORKG) took 0.2546977996826172s
Accuracy | Check Inverse Functional Property for Open Research Knowledge Graph (ORKG) took 0.24656200408935547s
Accuracy | Check Empty annotation labels for Open Research Knowledge Graph (ORKG) took 5.162456750869751s
Accuracy | Check White space in annotation for Open Research Knowledge Graph (ORKG) took 0.14754176139831543s
Accuracy | Check Datatype consistency for Open Research Knowledge Graph (ORKG) took 0.27069640159606934s
Consistency | Disjoint class check for Open Research Knowledge Graph (ORKG) took 0.17435550689697266s
Consistency | Check Misplaced properties for Open Research Knowledge Graph (ORKG) took 1.4349570274353027s
Consistency | Misplaced classes for Open Research Knowledge Graph (ORKG) took 0.91998291015625s
Consistency | Check Ontology hijacking for Open Research Knowledge Graph (ORKG) took 5.630746126174927s
Consistency | Check Invalid usage of undefined classes for Open Research Knowledge Graph (ORKG) took 1.3403100967407227s
Consistency | Check Invalid usage of undefined properties for Open Research Knowledge Graph (ORKG) took 2.26290225982666s
Conciseness | Check Extensional conciseness for Open Research Knowledge Graph (ORKG) took 0.28304314613342285s
Conciseness | Check Intensional conciseness for Open Research Knowledge Graph (ORKG) took 0.12478446960449219s
Security | Sign check for Open Research Knowledge Graph (ORKG) took 0.1785879135131836s
Availability | Check URIs Dereferenciability for Open Research Knowledge Graph (ORKG) took 2023.9725251197815s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.5380713939666748s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.020955324172973633s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0007991790771484375s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.7642974853515625e-05s
Interoperability | Check the re-using of existing vocabs for Open Research Knowledge Graph (ORKG) took 1.9073486328125e-06s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 6.9141387939453125e-06s
INFO | --- Analysis for orkg took 2304.8036892414093s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.9506657123565674s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0005714893341064453s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.2619922161102295s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020856618881225586s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.821487426757812e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 8.106231689453125e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 31.55428671836853s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 1.6188602447509766s
Availability | VoID file availability check for OSM Semantic Network took 0.0003876686096191406s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.26839590072631836s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.337860107421875e-05s
Believability | Calculation of trust value for OSM Semantic Network took 7.62939453125e-06s
INFO | --- Analysis for osm-semantic-network took 9.626157760620117s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 0.50534987449646s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.00025844573974609375s
Extra | Recovery of all triples for Open Transport Map @PSNC took 115.14488673210144s
Performance | Total latancy measurement for Open Transport Map @PSNC took 0.9983561038970947s
Amount of data | Number of triples check for Open Transport Map @PSNC took 8.361300945281982s
Interoperability | New terms check for Open Transport Map @PSNC took 15.02361536026001s
Versatility | Languages check for Open Transport Map @PSNC took 300.1681458950043s
Interpretability | Number of blank nodes check for Open Transport Map @PSNC took 3.3211119174957275s
Interpretability | RDF structures check for Open Transport Map @PSNC took 0.24626994132995605s
Versatility | Serialization formats check for Open Transport Map @PSNC took 9.747965574264526s
Availability | RDF dump link check for Open Transport Map @PSNC took 0.23369479179382324s
License | MR license check for Open Transport Map @PSNC took 0.4037320613861084s
License | HR license check for Open Transport Map @PSNC took 300.21408247947693s
Amount of data | Number of property check for Open Transport Map @PSNC took 0.25870633125305176s
Understandability | Number of label check for Open Transport Map @PSNC took 2.237370729446411s
Understandability | URI regex check for Open Transport Map @PSNC took 0.5435872077941895s
Understandability | Vocabs check for Open Transport Map @PSNC took 0.40345239639282227s
Verifiability | Authors check for Open Transport Map @PSNC took 0.21392226219177246s
Verifiability | Publishers check for Open Transport Map @PSNC took 0.25127363204956055s
Performance | Throughput check for Open Transport Map @PSNC took 11.505846738815308s
Amount of data | Check the number of entities for Open Transport Map @PSNC took 3.1948089599609375e-05s
Verifiability | Contribs. check for Open Transport Map @PSNC took 0.19406890869140625s
Interlinking | sameAs chians check for Open Transport Map @PSNC took 0.2053236961364746s
Interlinking | skos check for Open Transport Map @PSNC took 0.5152812004089355s
Interlinking | skos check for Open Transport Map @PSNC took 0.4406752586364746s
Timeliness | dataset update frequency check for Open Transport Map @PSNC took 6.4081361293792725s
Currency | Creation date check for Open Transport Map @PSNC took 0.4829373359680176s
Currency | Modification date check for Open Transport Map @PSNC took 0.22283411026000977s
Rep.Conc. | URIs length for Open Transport Map @PSNC took 155.73404908180237s
Interoperability | New vocabularies check for Open Transport Map @PSNC took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Open Transport Map @PSNC took 0.2106330394744873s
Accuracy | Check Functional Property for Open Transport Map @PSNC took 0.25095343589782715s
Accuracy | Check Inverse Functional Property for Open Transport Map @PSNC took 0.33435511589050293s
Accuracy | Check Empty annotation labels for Open Transport Map @PSNC took 46.546876192092896s
Accuracy | Check White space in annotation for Open Transport Map @PSNC took 2.6755564212799072s
Accuracy | Check Datatype consistency for Open Transport Map @PSNC took 2.6351566314697266s
Consistency | Disjoint class check for Open Transport Map @PSNC took 0.1934194564819336s
Consistency | Check Misplaced properties for Open Transport Map @PSNC took 79.91138076782227s
Consistency | Misplaced classes for Open Transport Map @PSNC took 8.495861053466797s
Consistency | Check Ontology hijacking for Open Transport Map @PSNC took 32.9715793132782s
Consistency | Check Invalid usage of undefined classes for Open Transport Map @PSNC took 1.3984489440917969s
Consistency | Check Invalid usage of undefined properties for Open Transport Map @PSNC took 82.09417057037354s
Conciseness | Check Extensional conciseness for Open Transport Map @PSNC took 2.761216163635254s
Conciseness | Check Intensional conciseness for Open Transport Map @PSNC took 0.6498587131500244s
Security | Sign check for Open Transport Map @PSNC took 0.8711791038513184s
Availability | Check URIs Dereferenciability for Open Transport Map @PSNC took 10.083687782287598s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 1.4748437404632568s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020694494247436523s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 4.363059997558594e-05s
Interoperability | Check the re-using of existing vocabs for Open Transport Map @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Open Transport Map @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for OTM took 2256.356969833374s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.29581165313720703s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 3.0279159545898438e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 7.3909759521484375e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 5.148743391036987s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.220008850097656e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2872121334075928s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.956390380859375e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-catalogue took 3.8043015003204346s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.3392181396484375e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.00035572052001953125s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.7005636692047119s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 3.8141086101531982s
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.0002605915069580078s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.2834949493408203s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 3.0517578125e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 3.789594888687134s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.2438507080078125e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.25948357582092285s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 3.7745120525360107s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.291534423828125e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.24587488174438477s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.020656347274780273s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 6.9141387939453125e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.8808486461639404s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.363059997558594e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2633655071258545s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 7.3909759521484375e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.8335766792297363s
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.0002524852752685547s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.2624545097351074s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020851612091064453s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 4.100799560546875e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 7.867813110351562e-06s
INFO | --- Analysis for oxpoints took 2.795477867126465s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.749584436416626s
Availability | VoID file availability check for Pali English Lexicon took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.2324669361114502s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.956390380859375e-05s
Believability | Calculation of trust value for Pali English Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for pali-english-lexicon took 6.856696844100952s
Availability | SPARQL endpoint availability check for PanLex took 0.365980863571167s
Availability | VoID file availability check for PanLex took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for PanLex took 0.2554454803466797s
Reputation | Calculation of the PageRank for PanLex took 0.020610570907592773s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.82012939453125e-05s
Believability | Calculation of trust value for PanLex took 7.3909759521484375e-06s
INFO | --- Analysis for panlex took 2.739412784576416s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.506111145019531e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.26658201217651367s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0205686092376709s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.7670135498046875e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 7.152557373046875e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 5.82066011428833s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 0.1311933994293213s
Availability | VoID file availability check for patents.data.gov.uk took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.26755309104919434s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020240306854248047s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.935264587402344e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 4.76837158203125e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.565566301345825s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.291534423828125e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0006709098815917969s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.278583288192749s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02057361602783203s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.886222839355469e-05s
Believability | Calculation of trust value for PDEV-Lemon took 6.4373016357421875e-06s
INFO | --- Analysis for pdev-lemon took 4.115338325500488s
Availability | SPARQL endpoint availability check for pdevlemon took 4.3392181396484375e-05s
Availability | VoID file availability check for pdevlemon took 0.0005495548248291016s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2661709785461426s
Reputation | Calculation of the PageRank for pdevlemon took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for pdevlemon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.8848648071289062e-05s
Believability | Calculation of trust value for pdevlemon took 8.106231689453125e-06s
INFO | --- Analysis for pdevlemon took 3.170588731765747s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.220008850097656e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.2671244144439697s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 8.058547973632812e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for periodo took 18.3945894241333s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.2438507080078125e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.2551391124725342s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00038433074951171875s
Believability | Calculation of trust value for Personal_Homepages took 7.152557373046875e-06s
INFO | --- Analysis for personal-homepages took 2.2844502925872803s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.410743713378906e-05s
Availability | VoID file availability check for Ontology of University People took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.285571813583374s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 3.075599670410156e-05s
Believability | Calculation of trust value for Ontology of University People took 7.62939453125e-06s
INFO | --- Analysis for PersonOnto took 2.363205909729004s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.154862403869629s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2608485221862793s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02057790756225586s
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.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.3113021850585938e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.3909759521484375e-06s
INFO | --- Analysis for PFKHS took 14.869841575622559s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.657862424850464s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006146430969238281s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2733278274536133s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2636184692382812e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.867813110351562e-06s
INFO | --- Analysis for PFRPPH took 12.319267272949219s
Availability | SPARQL endpoint availability check for PGxLOD took 0.4355933666229248s
Availability | VoID file availability check for PGxLOD took 0.0005633831024169922s
Extra | Recovery of all triples for PGxLOD took 2.314103603363037s
Performance | Total latancy measurement for PGxLOD took 0.8717694282531738s
Amount of data | Number of triples check for PGxLOD took 0.8675177097320557s
Interoperability | New terms check for PGxLOD took 2.0648674964904785s
Versatility | Languages check for PGxLOD took 60.24833130836487s
Interpretability | Number of blank nodes check for PGxLOD took 1.5926525592803955s
Interpretability | RDF structures check for PGxLOD took 0.3996846675872803s
Versatility | Serialization formats check for PGxLOD took 0.1979386806488037s
Availability | RDF dump link check for PGxLOD took 54.38065457344055s
License | MR license check for PGxLOD took 0.16183781623840332s
License | HR license check for PGxLOD took 60.27260422706604s
Amount of data | Number of property check for PGxLOD took 0.17049741744995117s
Understandability | Number of label check for PGxLOD took 0.8069782257080078s
Understandability | URI regex check for PGxLOD took 0.3117690086364746s
Understandability | Vocabs check for PGxLOD took 0.18232202529907227s
Verifiability | Authors check for PGxLOD took 0.16389966011047363s
Verifiability | Publishers check for PGxLOD took 0.166670560836792s
Performance | Throughput check for PGxLOD took 11.053089141845703s
Amount of data | Check the number of entities for PGxLOD took 0.12312006950378418s
Verifiability | Contribs. check for PGxLOD took 0.15563416481018066s
Interlinking | sameAs chians check for PGxLOD took 0.28649163246154785s
Interlinking | skos check for PGxLOD took 0.1918811798095703s
Interlinking | skos check for PGxLOD took 0.19713878631591797s
Timeliness | dataset update frequency check for PGxLOD took 0.15475201606750488s
Currency | Creation date check for PGxLOD took 0.33807969093322754s
Currency | Modification date check for PGxLOD took 0.3436868190765381s
Rep.Conc. | URIs length for PGxLOD took 6.751789093017578s
Interoperability | New vocabularies check for PGxLOD took 21.522043466567993s
Consistency | Deprecated classes/propertiers check for PGxLOD took 0.17047357559204102s
Accuracy | Check Functional Property for PGxLOD took 0.1940298080444336s
Accuracy | Check Inverse Functional Property for PGxLOD took 0.19516563415527344s
Accuracy | Check Empty annotation labels for PGxLOD took 1.0741162300109863s
Accuracy | Check White space in annotation for PGxLOD took 0.036748647689819336s
Accuracy | Check Datatype consistency for PGxLOD took 0.02835845947265625s
Consistency | Disjoint class check for PGxLOD took 0.16515517234802246s
Consistency | Check Misplaced properties for PGxLOD took 6.634881258010864s
Consistency | Misplaced classes for PGxLOD took 0.31319379806518555s
Consistency | Check Ontology hijacking for PGxLOD took 2.11396861076355s
Consistency | Check Invalid usage of undefined classes for PGxLOD took 1.2944977283477783s
Consistency | Check Invalid usage of undefined properties for PGxLOD took 7.136669635772705s
Conciseness | Check Extensional conciseness for PGxLOD took 0.03192615509033203s
Conciseness | Check Intensional conciseness for PGxLOD took 0.2606830596923828s
Security | Sign check for PGxLOD took 0.1928997039794922s
Availability | Check URIs Dereferenciability for PGxLOD took 1616.251387834549s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.9482302665710449s
Reputation | Calculation of the PageRank for PGxLOD took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for PGxLOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007421970367431641s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for PGxLOD took 29.174296140670776s
Believability | Calculation of trust value for PGxLOD took 7.3909759521484375e-06s
INFO | --- Analysis for PGxLOD took 2987.0997126102448s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 1.3057966232299805s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0006284713745117188s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.263547420501709s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 6.4373016357421875e-06s
INFO | --- Analysis for phoible took 6.898044586181641s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 4.291534423828125e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.000766754150390625s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.27934694290161133s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.020943164825439453s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.170967102050781e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 7.867813110351562e-06s
INFO | --- Analysis for PISM took 13.13271951675415s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 6.842613220214844e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.2570667266845703s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020708322525024414s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 9.5367431640625e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.2159347534179688e-05s
INFO | --- Analysis for planetdata-project-wiki took 2.4483962059020996s
Availability | SPARQL endpoint availability check for digitized plant specimen took 1.225583553314209s
Availability | VoID file availability check for digitized plant specimen took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.2669227123260498s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 7.128715515136719e-05s
Believability | Calculation of trust value for digitized plant specimen took 6.67572021484375e-06s
INFO | --- Analysis for plant-specimen took 3.6319565773010254s
Availability | SPARQL endpoint availability check for Pleiades took 5.602836608886719e-05s
Availability | VoID file availability check for Pleiades took 0.0005831718444824219s
Completeness | Calculation of interlinking completeness for Pleiades took 0.2610595226287842s
Reputation | Calculation of the PageRank for Pleiades took 0.021457672119140625s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.440017700195312e-05s
Believability | Calculation of trust value for Pleiades took 1.1444091796875e-05s
INFO | --- Analysis for pleiades took 13.542739391326904s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.315376281738281e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0003979206085205078s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.28914690017700195s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.020223617553710938s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 3.337860107421875e-05s
Believability | Calculation of trust value for podorozhnyk.com took 7.152557373046875e-06s
INFO | --- Analysis for podorozhnyk took 4.800776481628418s
Availability | SPARQL endpoint availability check for Poképédia took 4.363059997558594e-05s
Availability | VoID file availability check for Poképédia took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Poképédia took 0.26369166374206543s
Reputation | Calculation of the PageRank for Poképédia took 0.020044326782226562s
Interlinking | Calculation of Degree of Connection for Poképédia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Poképédia took 7.009506225585938e-05s
Believability | Calculation of trust value for Poképédia took 1.5735626220703125e-05s
INFO | --- Analysis for pokepedia-fr took 2.668220281600952s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.5299530029296875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.25816965103149414s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.224082946777344e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 6.9141387939453125e-06s
INFO | --- Analysis for polymath-virtual-library took 5.847498416900635s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 2.919642448425293s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0006401538848876953s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.24749541282653809s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3589859008789062e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 7.62939453125e-06s
INFO | --- Analysis for portuguese_prisons_releases took 7.311020851135254s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.1961669921875e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.25571417808532715s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 2.8848648071289062e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.152557373046875e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.866255283355713s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.291534423828125e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2524075508117676s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020689964294433594s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 3.0994415283203125e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 5.9604644775390625e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.883253574371338s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.1484832763671875e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.27895236015319824s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.02066802978515625s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 3.314018249511719e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 7.62939453125e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.9721412658691406s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 4.220008850097656e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.2687211036682129s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020563840866088867s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.0279159545898438e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 6.67572021484375e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.8864011764526367s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.00543212890625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.2662630081176758s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.0207517147064209s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 6.4373016357421875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.8468947410583496s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.2610461711883545s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 6.4373016357421875e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.913076639175415s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.25940442085266113s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.9802322387695312e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 5.9604644775390625e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.917769432067871s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.172325134277344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.2779519557952881s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.945378303527832s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.982948303222656e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.27738165855407715s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.9309208393096924s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.26329493522644043s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.9716579914093018s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 4.1961669921875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.26073694229125977s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.02028346061706543s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 9.775161743164062e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.95269513130188s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 5.2928924560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.25088953971862793s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 3.123283386230469e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.8455464839935303s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 6.890296936035156e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.26523637771606445s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 3.218650817871094e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.927696704864502s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2747642993927002s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.0994415283203125e-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.928910493850708s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.2613229751586914s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020741939544677734s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.8964920043945312s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.410743713378906e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2527916431427002s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 3.0994415283203125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.939708948135376s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.267692565917969e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0003037452697753906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.26392436027526855s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020855426788330078s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.409385681152344e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.910951614379883s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.315376281738281e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.25652456283569336s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.022211790084838867s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 3.24249267578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.8777916431427s
Availability | SPARQL endpoint availability check for prefix.cc took 4.3392181396484375e-05s
Availability | VoID file availability check for prefix.cc took 0.0005717277526855469s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.27939438819885254s
Reputation | Calculation of the PageRank for prefix.cc took 0.0206301212310791s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.00543212890625e-05s
Believability | Calculation of trust value for prefix.cc took 6.198883056640625e-06s
INFO | --- Analysis for prefix-cc took 3.2033863067626953s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 2.2745771408081055s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0005738735198974609s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.2681577205657959s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.887580871582031e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.1205673217773438e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 9.219192743301392s
Availability | SPARQL endpoint availability check for PreLex took 4.5638587474823s
Availability | VoID file availability check for PreLex took 0.0006487369537353516s
Completeness | Calculation of interlinking completeness for PreLex took 0.2844095230102539s
Reputation | Calculation of the PageRank for PreLex took 0.02060675621032715s
Interlinking | Calculation of Degree of Connection for PreLex took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for PreLex took 7.343292236328125e-05s
Believability | Calculation of trust value for PreLex took 6.67572021484375e-06s
INFO | --- Analysis for prelex took 13.372574806213379s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.285301446914673s
Availability | VoID file availability check for Prelinger Archives took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.28333616256713867s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020596027374267578s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 3.147125244140625e-05s
Believability | Calculation of trust value for Prelinger Archives took 6.9141387939453125e-06s
INFO | --- Analysis for prelinger_archives took 11.290808200836182s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 0.802314281463623s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0005338191986083984s
Extra | Recovery of all triples for PreMOn (Predicate Model for Ontologies) took 4.910115003585815s
Performance | Total latancy measurement for PreMOn (Predicate Model for Ontologies) took 0.873957633972168s
Amount of data | Number of triples check for PreMOn (Predicate Model for Ontologies) took 0.10520172119140625s
Interoperability | New terms check for PreMOn (Predicate Model for Ontologies) took 2.407836675643921s
Versatility | Languages check for PreMOn (Predicate Model for Ontologies) took 58.89756441116333s
Interpretability | Number of blank nodes check for PreMOn (Predicate Model for Ontologies) took 0.10782575607299805s
Security | Check HTTPS for PreMOn (Predicate Model for Ontologies) took 0.07450485229492188s
Interpretability | RDF structures check for PreMOn (Predicate Model for Ontologies) took 0.25447607040405273s
Versatility | Serialization formats check for PreMOn (Predicate Model for Ontologies) took 0.22809958457946777s
Availability | RDF dump link check for PreMOn (Predicate Model for Ontologies) took 0.18663573265075684s
License | MR license check for PreMOn (Predicate Model for Ontologies) took 0.3846628665924072s
License | HR license check for PreMOn (Predicate Model for Ontologies) took 0.9403767585754395s
Amount of data | Number of property check for PreMOn (Predicate Model for Ontologies) took 0.1862187385559082s
Understandability | Number of label check for PreMOn (Predicate Model for Ontologies) took 0.08719205856323242s
Understandability | URI regex check for PreMOn (Predicate Model for Ontologies) took 0.5516293048858643s
Understandability | Vocabs check for PreMOn (Predicate Model for Ontologies) took 0.3170967102050781s
Verifiability | Authors check for PreMOn (Predicate Model for Ontologies) took 0.19378376007080078s
Verifiability | Publishers check for PreMOn (Predicate Model for Ontologies) took 0.2651560306549072s
Performance | Throughput check for PreMOn (Predicate Model for Ontologies) took 11.159408807754517s
Amount of data | Check the number of entities for PreMOn (Predicate Model for Ontologies) took 3.409385681152344e-05s
Verifiability | Contribs. check for PreMOn (Predicate Model for Ontologies) took 0.3636586666107178s
Interlinking | sameAs chians check for PreMOn (Predicate Model for Ontologies) took 0.36301684379577637s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.46085190773010254s
Interlinking | skos check for PreMOn (Predicate Model for Ontologies) took 0.3307075500488281s
Timeliness | dataset update frequency check for PreMOn (Predicate Model for Ontologies) took 0.3620641231536865s
Currency | Creation date check for PreMOn (Predicate Model for Ontologies) took 0.7226121425628662s
Currency | Modification date check for PreMOn (Predicate Model for Ontologies) took 0.721538782119751s
Rep.Conc. | URIs length for PreMOn (Predicate Model for Ontologies) took 4.2793262004852295s
Interoperability | New vocabularies check for PreMOn (Predicate Model for Ontologies) took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for PreMOn (Predicate Model for Ontologies) took 0.3074352741241455s
Accuracy | Check Empty annotation labels for PreMOn (Predicate Model for Ontologies) took 1.6830191612243652s
Accuracy | Check White space in annotation for PreMOn (Predicate Model for Ontologies) took 0.08207058906555176s
Accuracy | Check Datatype consistency for PreMOn (Predicate Model for Ontologies) took 0.08497142791748047s
Consistency | Disjoint class check for PreMOn (Predicate Model for Ontologies) took 0.23261213302612305s
Consistency | Check Misplaced properties for PreMOn (Predicate Model for Ontologies) took 1.9288678169250488s
Consistency | Misplaced classes for PreMOn (Predicate Model for Ontologies) took 0.43939733505249023s
Consistency | Check Ontology hijacking for PreMOn (Predicate Model for Ontologies) took 2.696195363998413s
Consistency | Check Invalid usage of undefined classes for PreMOn (Predicate Model for Ontologies) took 1.3302435874938965s
Consistency | Check Invalid usage of undefined properties for PreMOn (Predicate Model for Ontologies) took 3.0530476570129395s
Conciseness | Check Extensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.09220194816589355s
Conciseness | Check Intensional conciseness for PreMOn (Predicate Model for Ontologies) took 0.19954752922058105s
Security | Sign check for PreMOn (Predicate Model for Ontologies) took 0.21200037002563477s
Availability | Check URIs Dereferenciability for PreMOn (Predicate Model for Ontologies) took 1066.9381415843964s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 1.0070245265960693s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.02133488655090332s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 0.00010967254638671875s
Interoperability | Check the re-using of existing vocabs for PreMOn (Predicate Model for Ontologies) took 2.1457672119140625e-06s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 8.106231689453125e-06s
INFO | --- Analysis for premon took 1195.3769216537476s
Availability | SPARQL endpoint availability check for Previsible took 4.5299530029296875e-05s
Availability | VoID file availability check for Previsible took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Previsible took 0.25216174125671387s
Reputation | Calculation of the PageRank for Previsible took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for Previsible took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Previsible took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.2874603271484375e-05s
Believability | Calculation of trust value for Previsible took 8.106231689453125e-06s
INFO | --- Analysis for Previsible took 3.7512991428375244s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 4.458427429199219e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.25506162643432617s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.5789947509765625e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 6.67572021484375e-06s
INFO | --- Analysis for princeton-library-findingaids took 4.734330654144287s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 0.500521183013916s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.7320272922515869s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for PrinParLat took 4.721300840377808s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.4862799644470215s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.25971007347106934s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.153915405273438e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.62939453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.704192638397217s
Availability | SPARQL endpoint availability check for Prior Panel took 7.891654968261719e-05s
Availability | VoID file availability check for Prior Panel took 0.00047969818115234375s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.27106618881225586s
Reputation | Calculation of the PageRank for Prior Panel took 0.0207974910736084s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0010328292846679688s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 4.267692565917969e-05s
Believability | Calculation of trust value for Prior Panel took 7.62939453125e-06s
INFO | --- Analysis for Prior_Panel took 2.43955659866333s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.267692565917969e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.276228666305542s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.001005411148071289s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.956390380859375e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 6.9141387939453125e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.9115335941314697s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.315376281738281e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.25762939453125s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.1948089599609375e-05s
Believability | Calculation of trust value for Procomún SPARQL took 8.58306884765625e-06s
INFO | --- Analysis for procomun-sparql took 2.792915105819702s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.172325134277344e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.2815127372741699s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 8.58306884765625e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.9518890380859375s
Availability | SPARQL endpoint availability check for ProductDB took 2.979489326477051s
Availability | VoID file availability check for ProductDB took 0.0006747245788574219s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2635164260864258s
Reputation | Calculation of the PageRank for ProductDB took 0.021285295486450195s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0008652210235595703s
Interlinking | Calculation of Clustering coefficient for ProductDB took 8.034706115722656e-05s
Believability | Calculation of trust value for ProductDB took 7.3909759521484375e-06s
INFO | --- Analysis for productdb took 7.080660343170166s
Availability | SPARQL endpoint availability check for Product Types Ontology took 5.793571472167969e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0005514621734619141s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.2570986747741699s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007758140563964844s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.772445678710938e-05s
Believability | Calculation of trust value for Product Types Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for productontology took 3.3506391048431396s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.601478576660156e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.25864434242248535s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 8.106231689453125e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 6.938659429550171s
Availability | SPARQL endpoint availability check for provenanceweb took 0.054970741271972656s
Availability | VoID file availability check for provenanceweb took 0.0006153583526611328s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.268552303314209s
Reputation | Calculation of the PageRank for provenanceweb took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0008196830749511719s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 8.034706115722656e-05s
Believability | Calculation of trust value for provenanceweb took 7.62939453125e-06s
INFO | --- Analysis for provenanceweb took 66.11435437202454s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.3392181396484375e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0006687641143798828s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.2699861526489258s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007755756378173828s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010371208190917969s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 7.152557373046875e-06s
INFO | --- Analysis for proyectoapadrina took 9.42039966583252s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 25.378276824951172s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.0008380413055419922s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2891988754272461s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02074289321899414s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.337860107421875e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 4.5299530029296875e-06s
INFO | --- Analysis for pscs-catalogue took 125.33829164505005s
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.0005955696105957031s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.2878880500793457s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020595788955688477s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.271766662597656e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.867813110351562e-06s
INFO | --- Analysis for psh-subject-headings took 3.7544403076171875s
Availability | SPARQL endpoint availability check for Depression took 0.3019895553588867s
Availability | VoID file availability check for Depression took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for Depression took 0.2696535587310791s
Reputation | Calculation of the PageRank for Depression took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for Depression took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Depression took 3.0994415283203125e-05s
Believability | Calculation of trust value for Depression took 7.867813110351562e-06s
INFO | --- Analysis for Psychology took 3.089050531387329s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.38690185546875e-05s
Availability | VoID file availability check for PubChem RDF took 0.0003914833068847656s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.2568349838256836s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 4.076957702636719e-05s
Believability | Calculation of trust value for PubChem RDF took 9.775161743164062e-06s
INFO | --- Analysis for PubChem_RDF took 6.2041356563568115s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.1961669921875e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.29089927673339844s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 3.0040740966796875e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 8.106231689453125e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.9439518451690674s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 0.7634000778198242s
Availability | VoID file availability check for Public Spending in Greece took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.25999021530151367s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.82012939453125e-05s
Believability | Calculation of trust value for Public Spending in Greece took 6.198883056640625e-06s
INFO | --- Analysis for public-spending-in-greece took 8.524487495422363s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.172325134277344e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.267850399017334s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 3.0994415283203125e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 6.67572021484375e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.889866590499878s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 0.2551391124725342s
Availability | VoID file availability check for Publications Office Authority tables took 0.0007431507110595703s
Extra | Recovery of all triples for Publications Office Authority tables took 111.70926141738892s
Performance | Total latancy measurement for Publications Office Authority tables took 0.6118652820587158s
Amount of data | Number of triples check for Publications Office Authority tables took 0.6123905181884766s
Interoperability | New terms check for Publications Office Authority tables took 12.207427263259888s
Versatility | Languages check for Publications Office Authority tables took 300.0686995983124s
Interpretability | Number of blank nodes check for Publications Office Authority tables took 2.3051154613494873s
Security | Check HTTPS for Publications Office Authority tables took 0.34031081199645996s
Interpretability | RDF structures check for Publications Office Authority tables took 0.3894309997558594s
Versatility | Serialization formats check for Publications Office Authority tables took 3.9723427295684814s
Availability | RDF dump link check for Publications Office Authority tables took 0.3130147457122803s
License | MR license check for Publications Office Authority tables took 0.3703269958496094s
License | HR license check for Publications Office Authority tables took 300.00816321372986s
Amount of data | Number of property check for Publications Office Authority tables took 0.18767571449279785s
Understandability | Number of label check for Publications Office Authority tables took 9.730775117874146s
Understandability | URI regex check for Publications Office Authority tables took 0.509105920791626s
Understandability | Vocabs check for Publications Office Authority tables took 0.08722972869873047s
Verifiability | Authors check for Publications Office Authority tables took 0.23122000694274902s
Verifiability | Publishers check for Publications Office Authority tables took 0.28275537490844727s
Performance | Throughput check for Publications Office Authority tables took 10.590035200119019s
Amount of data | Check the number of entities for Publications Office Authority tables took 7.748603820800781e-05s
Verifiability | Contribs. check for Publications Office Authority tables took 0.2169506549835205s
Interlinking | sameAs chians check for Publications Office Authority tables took 2.6138551235198975s
Interlinking | skos check for Publications Office Authority tables took 0.18946623802185059s
Interlinking | skos check for Publications Office Authority tables took 0.15236616134643555s
Timeliness | dataset update frequency check for Publications Office Authority tables took 0.16589045524597168s
Currency | Creation date check for Publications Office Authority tables took 0.36574292182922363s
Currency | Modification date check for Publications Office Authority tables took 0.18638086318969727s
Rep.Conc. | URIs length for Publications Office Authority tables took 238.23968362808228s
Interoperability | New vocabularies check for Publications Office Authority tables took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for Publications Office Authority tables took 0.19170379638671875s
Accuracy | Check Functional Property for Publications Office Authority tables took 0.21204352378845215s
Accuracy | Check Inverse Functional Property for Publications Office Authority tables took 0.18550705909729004s
Accuracy | Check Empty annotation labels for Publications Office Authority tables took 34.160375118255615s
Accuracy | Check White space in annotation for Publications Office Authority tables took 3.104691982269287s
Accuracy | Check Datatype consistency for Publications Office Authority tables took 2.605081081390381s
Consistency | Disjoint class check for Publications Office Authority tables took 0.22524666786193848s
Consistency | Check Misplaced properties for Publications Office Authority tables took 78.52569341659546s
Consistency | Misplaced classes for Publications Office Authority tables took 8.437602519989014s
Consistency | Check Ontology hijacking for Publications Office Authority tables took 42.428215742111206s
Consistency | Check Invalid usage of undefined classes for Publications Office Authority tables took 1.6373145580291748s
Consistency | Check Invalid usage of undefined properties for Publications Office Authority tables took 78.94639921188354s
Conciseness | Check Extensional conciseness for Publications Office Authority tables took 2.984066963195801s
Conciseness | Check Intensional conciseness for Publications Office Authority tables took 0.4672996997833252s
Security | Sign check for Publications Office Authority tables took 0.1319582462310791s
Availability | Check URIs Dereferenciability for Publications Office Authority tables took 8.880318880081177s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 1.3726017475128174s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 4.9114227294921875e-05s
Interoperability | Check the re-using of existing vocabs for Publications Office Authority tables took 1.9073486328125e-06s
Believability | Calculation of trust value for Publications Office Authority tables took 1.1444091796875e-05s
INFO | --- Analysis for publications_office_authority_tables took 14610.395517110825s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 6.842613220214844e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.2789599895477295s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.021820068359375s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0008533000946044922s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 3.552436828613281e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 8.821487426757812e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 5.249586582183838s
Availability | SPARQL endpoint availability check for QBOAirbase took 5.316734313964844e-05s
Availability | VoID file availability check for QBOAirbase took 0.0007960796356201172s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.2687208652496338s
Reputation | Calculation of the PageRank for QBOAirbase took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.52587890625e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 8.511543273925781e-05s
Believability | Calculation of trust value for QBOAirbase took 1.2159347534179688e-05s
INFO | --- Analysis for qboairbase took 138.56346106529236s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.2438507080078125e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.6776649951934814s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020441532135009766s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.86102294921875e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.3909759521484375e-06s
INFO | --- Analysis for qualitywebdata-org took 4.208469390869141s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.267692565917969e-05s
Availability | VoID file availability check for Qualité de l'air took 0.00033545494079589844s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.2553253173828125s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.8371810913085938e-05s
Believability | Calculation of trust value for Qualité de l'air took 7.152557373046875e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.7708656787872314s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.4345855712890625e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.0003528594970703125s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.8237485885620117s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 2.9802322387695312e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 7.152557373046875e-06s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 58.8897819519043s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.48938608169555664s
Availability | VoID file availability check for Querolus in LiLa took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.6988403797149658s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.719329833984375e-05s
Believability | Calculation of trust value for Querolus in LiLa took 6.67572021484375e-06s
INFO | --- Analysis for Querolus took 4.746930837631226s
Availability | SPARQL endpoint availability check for Quotations Book took 4.076957702636719e-05s
Availability | VoID file availability check for Quotations Book took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.2543954849243164s
Reputation | Calculation of the PageRank for Quotations Book took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for Quotations Book took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 2.8371810913085938e-05s
Believability | Calculation of trust value for Quotations Book took 1.33514404296875e-05s
INFO | --- Analysis for quotations_book took 3.375673770904541s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.410743713378906e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.24574828147888184s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020338773727416992s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for r4r took 3.2941060066223145s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.4741230010986328s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007154941558837891s
Extra | Recovery of all triples for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 72.18089270591736s
Performance | Total latancy measurement for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.7027087211608887s
Amount of data | Number of triples check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 3.592880964279175s
Interoperability | New terms check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.9223685264587402s
Versatility | Languages check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.360076427459717s
Interpretability | Number of blank nodes check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.49214768409729s
Interpretability | RDF structures check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1531996726989746s
Versatility | Serialization formats check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14274263381958008s
Availability | RDF dump link check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14021682739257812s
License | MR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14182567596435547s
License | HR license check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14214777946472168s
Amount of data | Number of property check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1291508674621582s
Understandability | Number of label check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14135456085205078s
Understandability | URI regex check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.3028864860534668s
Understandability | Vocabs check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13088726997375488s
Verifiability | Authors check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.14158868789672852s
Verifiability | Publishers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1414477825164795s
Performance | Throughput check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 11.000924825668335s
Amount of data | Check the number of entities for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.224082946777344e-05s
Verifiability | Contribs. check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1298813819885254s
Interlinking | sameAs chians check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12983059883117676s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13146066665649414s
Interlinking | skos check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15117383003234863s
Timeliness | dataset update frequency check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15304970741271973s
Currency | Creation date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2625272274017334s
Currency | Modification date check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.296954870223999s
Rep.Conc. | URIs length for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 16.88967990875244s
Interoperability | New vocabularies check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15023350715637207s
Accuracy | Check Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.12759876251220703s
Accuracy | Check Inverse Functional Property for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1293783187866211s
Accuracy | Check Empty annotation labels for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15160417556762695s
Accuracy | Check White space in annotation for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.8358230590820312e-05s
Consistency | Disjoint class check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.13862180709838867s
Consistency | Check Misplaced properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.77716588973999s
Consistency | Check Ontology hijacking for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 10.608620166778564s
Consistency | Check Invalid usage of undefined properties for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.759875297546387s
Conciseness | Check Extensional conciseness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.00014925003051757812s
Security | Sign check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.15628981590270996s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.2939906120300293s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.021386384963989258s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 5.1021575927734375e-05s
Interoperability | Check the re-using of existing vocabs for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 2.1457672119140625e-06s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.152557373046875e-06s
INFO | --- Analysis for racai-legalnero took 180.1584484577179s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 6.365776062011719e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0005960464477539062s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.26765990257263184s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007586479187011719s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.147125244140625e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 3.170967102050781e-05s
INFO | --- Analysis for racai-llod-corola-we took 2.9488425254821777s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 0.13132572174072266s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005249977111816406s
Extra | Recovery of all triples for PARSEME-Ro corpus took 69.04995608329773s
Performance | Total latancy measurement for PARSEME-Ro corpus took 0.6786181926727295s
Amount of data | Number of triples check for PARSEME-Ro corpus took 6.720800876617432s
Interoperability | New terms check for PARSEME-Ro corpus took 2.0930628776550293s
Versatility | Languages check for PARSEME-Ro corpus took 19.129751205444336s
Interpretability | Number of blank nodes check for PARSEME-Ro corpus took 5.479668617248535s
Interpretability | RDF structures check for PARSEME-Ro corpus took 0.13222002983093262s
Versatility | Serialization formats check for PARSEME-Ro corpus took 0.14313793182373047s
Availability | RDF dump link check for PARSEME-Ro corpus took 0.14056801795959473s
License | MR license check for PARSEME-Ro corpus took 0.15241527557373047s
License | HR license check for PARSEME-Ro corpus took 10.140475988388062s
Amount of data | Number of property check for PARSEME-Ro corpus took 0.14063763618469238s
Understandability | Number of label check for PARSEME-Ro corpus took 0.17555642127990723s
Understandability | URI regex check for PARSEME-Ro corpus took 0.28153324127197266s
Understandability | Vocabs check for PARSEME-Ro corpus took 0.14165806770324707s
Verifiability | Authors check for PARSEME-Ro corpus took 0.1417102813720703s
Verifiability | Publishers check for PARSEME-Ro corpus took 0.15319466590881348s
Performance | Throughput check for PARSEME-Ro corpus took 10.981738328933716s
Amount of data | Check the number of entities for PARSEME-Ro corpus took 6.866455078125e-05s
Verifiability | Contribs. check for PARSEME-Ro corpus took 0.13029694557189941s
Interlinking | sameAs chians check for PARSEME-Ro corpus took 0.13039374351501465s
Interlinking | skos check for PARSEME-Ro corpus took 0.1421201229095459s
Interlinking | skos check for PARSEME-Ro corpus took 0.1417381763458252s
Timeliness | dataset update frequency check for PARSEME-Ro corpus took 0.1524519920349121s
Currency | Creation date check for PARSEME-Ro corpus took 0.282686710357666s
Currency | Modification date check for PARSEME-Ro corpus took 0.2711927890777588s
Rep.Conc. | URIs length for PARSEME-Ro corpus took 74.996258020401s
Interoperability | New vocabularies check for PARSEME-Ro corpus took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for PARSEME-Ro corpus took 0.1299142837524414s
Accuracy | Check Functional Property for PARSEME-Ro corpus took 0.14036917686462402s
Accuracy | Check Inverse Functional Property for PARSEME-Ro corpus took 0.15158557891845703s
Accuracy | Check Empty annotation labels for PARSEME-Ro corpus took 4.417734146118164s
Accuracy | Check White space in annotation for PARSEME-Ro corpus took 0.23577499389648438s
Consistency | Disjoint class check for PARSEME-Ro corpus took 0.14399027824401855s
Consistency | Check Misplaced properties for PARSEME-Ro corpus took 10.937921524047852s
Consistency | Check Ontology hijacking for PARSEME-Ro corpus took 36.207215547561646s
Consistency | Check Invalid usage of undefined properties for PARSEME-Ro corpus took 13.16736888885498s
Conciseness | Check Extensional conciseness for PARSEME-Ro corpus took 0.00015163421630859375s
Security | Sign check for PARSEME-Ro corpus took 0.13906097412109375s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 1.2195484638214111s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020775794982910156s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007948875427246094s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 5.221366882324219e-05s
Interoperability | Check the re-using of existing vocabs for PARSEME-Ro corpus took 2.1457672119140625e-06s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.6927719116210938e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 306.64137387275696s
Availability | SPARQL endpoint availability check for RoLEX took 0.1285407543182373s
Availability | VoID file availability check for RoLEX took 0.0006763935089111328s
Extra | Recovery of all triples for RoLEX took 69.50790810585022s
Performance | Total latancy measurement for RoLEX took 0.6974246501922607s
Amount of data | Number of triples check for RoLEX took 1.6442911624908447s
Interoperability | New terms check for RoLEX took 1.6909680366516113s
Versatility | Languages check for RoLEX took 4.452623605728149s
Interpretability | Number of blank nodes check for RoLEX took 1.0953330993652344s
Interpretability | RDF structures check for RoLEX took 0.15245676040649414s
Versatility | Serialization formats check for RoLEX took 0.13063788414001465s
Availability | RDF dump link check for RoLEX took 0.15156888961791992s
License | MR license check for RoLEX took 0.15270066261291504s
License | HR license check for RoLEX took 0.1522536277770996s
Amount of data | Number of property check for RoLEX took 0.15148329734802246s
Understandability | Number of label check for RoLEX took 0.1532132625579834s
Understandability | URI regex check for RoLEX took 0.2802586555480957s
Understandability | Vocabs check for RoLEX took 0.1297001838684082s
Verifiability | Authors check for RoLEX took 0.14789462089538574s
Verifiability | Publishers check for RoLEX took 0.1514580249786377s
Performance | Throughput check for RoLEX took 10.975696802139282s
Amount of data | Check the number of entities for RoLEX took 0.0001087188720703125s
Verifiability | Contribs. check for RoLEX took 0.14054036140441895s
Interlinking | sameAs chians check for RoLEX took 0.140578031539917s
Interlinking | skos check for RoLEX took 0.14093923568725586s
Interlinking | skos check for RoLEX took 0.14138102531433105s
Timeliness | dataset update frequency check for RoLEX took 0.1425635814666748s
Currency | Creation date check for RoLEX took 0.28382086753845215s
Currency | Modification date check for RoLEX took 0.28090429306030273s
Rep.Conc. | URIs length for RoLEX took 54.62038564682007s
Interoperability | New vocabularies check for RoLEX took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for RoLEX took 0.15321946144104004s
Accuracy | Check Functional Property for RoLEX took 0.14069676399230957s
Accuracy | Check Inverse Functional Property for RoLEX took 0.14106416702270508s
Consistency | Disjoint class check for RoLEX took 0.15211224555969238s
Consistency | Check Misplaced properties for RoLEX took 2.468816041946411s
Consistency | Check Ontology hijacking for RoLEX took 18.32368302345276s
Consistency | Check Invalid usage of undefined properties for RoLEX took 3.8493542671203613s
Conciseness | Check Extensional conciseness for RoLEX took 0.00013256072998046875s
Security | Sign check for RoLEX took 0.13791966438293457s
Completeness | Calculation of interlinking completeness for RoLEX took 0.74717116355896s
Reputation | Calculation of the PageRank for RoLEX took 0.020648956298828125s
Interlinking | Calculation of Degree of Connection for RoLEX took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RoLEX took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for RoLEX took 3.0279159545898438e-05s
Interoperability | Check the re-using of existing vocabs for RoLEX took 1.9073486328125e-06s
Believability | Calculation of trust value for RoLEX took 7.3909759521484375e-06s
INFO | --- Analysis for racai-llod-rolex took 195.23843717575073s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.410743713378906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0005743503570556641s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.6954898834228516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.9325485229492188e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 3.5825624465942383s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.506111145019531e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.0006992816925048828s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.6927900314331055s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020512104034423828s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007410049438476562s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 3.075599670410156e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 7.3909759521484375e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.9766013622283936s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.57763671875e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0005950927734375s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.2783517837524414s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020746231079101562s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.123283386230469e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 3.9129703044891357s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.410743713378906e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0005979537963867188s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2929191589355469s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.9087066650390625e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.7423152923583984s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 0.14309477806091309s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0007302761077880859s
Extra | Recovery of all triples for ROBIN Technical Acquisition Speech Corpus took 27.596646070480347s
Performance | Total latancy measurement for ROBIN Technical Acquisition Speech Corpus took 0.6968686580657959s
Amount of data | Number of triples check for ROBIN Technical Acquisition Speech Corpus took 0.3050343990325928s
Interoperability | New terms check for ROBIN Technical Acquisition Speech Corpus took 1.489245891571045s
Versatility | Languages check for ROBIN Technical Acquisition Speech Corpus took 0.6424534320831299s
Interpretability | Number of blank nodes check for ROBIN Technical Acquisition Speech Corpus took 0.31428003311157227s
Interpretability | RDF structures check for ROBIN Technical Acquisition Speech Corpus took 0.1506643295288086s
Versatility | Serialization formats check for ROBIN Technical Acquisition Speech Corpus took 0.12966418266296387s
Availability | RDF dump link check for ROBIN Technical Acquisition Speech Corpus took 0.14633870124816895s
License | MR license check for ROBIN Technical Acquisition Speech Corpus took 0.1294078826904297s
License | HR license check for ROBIN Technical Acquisition Speech Corpus took 0.15846014022827148s
Amount of data | Number of property check for ROBIN Technical Acquisition Speech Corpus took 0.1391448974609375s
Understandability | Number of label check for ROBIN Technical Acquisition Speech Corpus took 0.1442108154296875s
Understandability | URI regex check for ROBIN Technical Acquisition Speech Corpus took 0.2679569721221924s
Understandability | Vocabs check for ROBIN Technical Acquisition Speech Corpus took 0.14446592330932617s
Verifiability | Authors check for ROBIN Technical Acquisition Speech Corpus took 0.1523914337158203s
Verifiability | Publishers check for ROBIN Technical Acquisition Speech Corpus took 0.13964152336120605s
Performance | Throughput check for ROBIN Technical Acquisition Speech Corpus took 10.679784059524536s
Amount of data | Check the number of entities for ROBIN Technical Acquisition Speech Corpus took 7.414817810058594e-05s
Verifiability | Contribs. check for ROBIN Technical Acquisition Speech Corpus took 0.14095520973205566s
Interlinking | sameAs chians check for ROBIN Technical Acquisition Speech Corpus took 0.14069151878356934s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.14254975318908691s
Interlinking | skos check for ROBIN Technical Acquisition Speech Corpus took 0.152815580368042s
Timeliness | dataset update frequency check for ROBIN Technical Acquisition Speech Corpus took 0.15382075309753418s
Currency | Creation date check for ROBIN Technical Acquisition Speech Corpus took 0.29491186141967773s
Currency | Modification date check for ROBIN Technical Acquisition Speech Corpus took 0.30431389808654785s
Rep.Conc. | URIs length for ROBIN Technical Acquisition Speech Corpus took 3.003351926803589s
Interoperability | New vocabularies check for ROBIN Technical Acquisition Speech Corpus took 8.58306884765625e-06s
Consistency | Deprecated classes/propertiers check for ROBIN Technical Acquisition Speech Corpus took 0.12792754173278809s
Accuracy | Check Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.13799095153808594s
Accuracy | Check Inverse Functional Property for ROBIN Technical Acquisition Speech Corpus took 0.14003372192382812s
Accuracy | Check Empty annotation labels for ROBIN Technical Acquisition Speech Corpus took 0.38382434844970703s
Accuracy | Check White space in annotation for ROBIN Technical Acquisition Speech Corpus took 0.009616613388061523s
Accuracy | Check Datatype consistency for ROBIN Technical Acquisition Speech Corpus took 1.1977145671844482s
Consistency | Disjoint class check for ROBIN Technical Acquisition Speech Corpus took 0.12894082069396973s
Consistency | Check Misplaced properties for ROBIN Technical Acquisition Speech Corpus took 0.5230824947357178s
Consistency | Check Ontology hijacking for ROBIN Technical Acquisition Speech Corpus took 2.494600772857666s
Consistency | Check Invalid usage of undefined classes for ROBIN Technical Acquisition Speech Corpus took 1.3103125095367432s
Consistency | Check Invalid usage of undefined properties for ROBIN Technical Acquisition Speech Corpus took 1.6790671348571777s
Conciseness | Check Extensional conciseness for ROBIN Technical Acquisition Speech Corpus took 0.8450989723205566s
Security | Sign check for ROBIN Technical Acquisition Speech Corpus took 0.13964605331420898s
Availability | Check URIs Dereferenciability for ROBIN Technical Acquisition Speech Corpus took 10812.298464298248s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.786675214767456s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.02130746841430664s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for ROBIN Technical Acquisition Speech Corpus took 1.9073486328125e-06s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-rtasc took 10889.121872663498s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 0.12853431701660156s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0006451606750488281s
Extra | Recovery of all triples for SiMoNERo - the Romanian medical treebank took 77.09831118583679s
Performance | Total latancy measurement for SiMoNERo - the Romanian medical treebank took 0.7237496376037598s
Amount of data | Number of triples check for SiMoNERo - the Romanian medical treebank took 1.0149097442626953s
Interoperability | New terms check for SiMoNERo - the Romanian medical treebank took 1.493781328201294s
Versatility | Languages check for SiMoNERo - the Romanian medical treebank took 2.4609086513519287s
Interpretability | Number of blank nodes check for SiMoNERo - the Romanian medical treebank took 0.7997004985809326s
Interpretability | RDF structures check for SiMoNERo - the Romanian medical treebank took 0.13187575340270996s
Versatility | Serialization formats check for SiMoNERo - the Romanian medical treebank took 0.14207839965820312s
Availability | RDF dump link check for SiMoNERo - the Romanian medical treebank took 0.14104485511779785s
License | MR license check for SiMoNERo - the Romanian medical treebank took 0.14205002784729004s
License | HR license check for SiMoNERo - the Romanian medical treebank took 4.540586471557617s
Amount of data | Number of property check for SiMoNERo - the Romanian medical treebank took 0.1519317626953125s
Understandability | Number of label check for SiMoNERo - the Romanian medical treebank took 0.1466982364654541s
Understandability | URI regex check for SiMoNERo - the Romanian medical treebank took 0.274066686630249s
Understandability | Vocabs check for SiMoNERo - the Romanian medical treebank took 0.13034343719482422s
Verifiability | Authors check for SiMoNERo - the Romanian medical treebank took 0.14171695709228516s
Verifiability | Publishers check for SiMoNERo - the Romanian medical treebank took 0.15263819694519043s
Performance | Throughput check for SiMoNERo - the Romanian medical treebank took 10.955268859863281s
Amount of data | Check the number of entities for SiMoNERo - the Romanian medical treebank took 8.034706115722656e-05s
Verifiability | Contribs. check for SiMoNERo - the Romanian medical treebank took 0.1522541046142578s
Interlinking | sameAs chians check for SiMoNERo - the Romanian medical treebank took 0.14223194122314453s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.15242695808410645s
Interlinking | skos check for SiMoNERo - the Romanian medical treebank took 0.14110708236694336s
Timeliness | dataset update frequency check for SiMoNERo - the Romanian medical treebank took 0.1533052921295166s
Currency | Creation date check for SiMoNERo - the Romanian medical treebank took 0.27327704429626465s
Currency | Modification date check for SiMoNERo - the Romanian medical treebank took 0.29438328742980957s
Rep.Conc. | URIs length for SiMoNERo - the Romanian medical treebank took 8.611256837844849s
Interoperability | New vocabularies check for SiMoNERo - the Romanian medical treebank took 5.3882598876953125e-05s
Consistency | Deprecated classes/propertiers check for SiMoNERo - the Romanian medical treebank took 0.1468343734741211s
Accuracy | Check Functional Property for SiMoNERo - the Romanian medical treebank took 0.12987279891967773s
Accuracy | Check Inverse Functional Property for SiMoNERo - the Romanian medical treebank took 0.1296839714050293s
Accuracy | Check Empty annotation labels for SiMoNERo - the Romanian medical treebank took 0.7893176078796387s
Accuracy | Check White space in annotation for SiMoNERo - the Romanian medical treebank took 0.0202786922454834s
Consistency | Disjoint class check for SiMoNERo - the Romanian medical treebank took 0.1385805606842041s
Consistency | Check Misplaced properties for SiMoNERo - the Romanian medical treebank took 1.6178598403930664s
Consistency | Check Ontology hijacking for SiMoNERo - the Romanian medical treebank took 6.8946380615234375s
Consistency | Check Invalid usage of undefined properties for SiMoNERo - the Romanian medical treebank took 2.8591346740722656s
Conciseness | Check Extensional conciseness for SiMoNERo - the Romanian medical treebank took 0.00014400482177734375s
Security | Sign check for SiMoNERo - the Romanian medical treebank took 0.15041518211364746s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.25035905838012695s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.020777225494384766s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.0279159545898438e-05s
Interoperability | Check the re-using of existing vocabs for SiMoNERo - the Romanian medical treebank took 1.6689300537109375e-06s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-simonero took 144.37903952598572s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.27807092666625977s
Availability | VoID file availability check for Rådata nå! took 0.0005733966827392578s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.27744102478027344s
Reputation | Calculation of the PageRank for Rådata nå! took 0.020258665084838867s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.058547973632812e-05s
Believability | Calculation of trust value for Rådata nå! took 7.62939453125e-06s
INFO | --- Analysis for radatana took 5.304451942443848s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.291534423828125e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0007688999176025391s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.26843690872192383s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.6716461181640625e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 7.152557373046875e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 17.03775906562805s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.363059997558594e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.2551264762878418s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 2.6464462280273438e-05s
Believability | Calculation of trust value for Raphael Research Resource took 8.106231689453125e-06s
INFO | --- Analysis for raphaelresearchresource took 4.309001684188843s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 12.600812673568726s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0007388591766357422s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2809271812438965s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020185470581054688s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 2.6702880859375e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 7.3909759521484375e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 28.345860481262207s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 392.5129601955414s
Availability | VoID file availability check for Polish LGU financial statements took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.2574005126953125s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021034717559814453s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0008330345153808594s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 4.1961669921875e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 6.9141387939453125e-06s
INFO | --- Analysis for Rb_PL_LGU took 667.4822494983673s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.506111145019531e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.701000452041626s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.020712852478027344s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 5.082849740982056s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.7233271598815918s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 4.661116123199463s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.482269287109375e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.23930931091308594s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.852631092071533s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.26621174812316895s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 2.956390380859375e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.88703989982605s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 5.7697296142578125e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.24870038032531738s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020395755767822266s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 2.9325485229492188e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 9.059906005859375e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.817011594772339s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.4345855712890625e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2917747497558594s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020474672317504883s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.392333984375e-05s
Believability | Calculation of trust value for RDF Book Mashup took 6.9141387939453125e-06s
INFO | --- Analysis for rdf-book-mashup took 3.4598426818847656s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.3392181396484375e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.27730894088745117s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.02032780647277832s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00010585784912109375s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 7.152557373046875e-06s
INFO | --- Analysis for rdfize-lastfm took 2.4373040199279785s
Availability | SPARQL endpoint availability check for RDFLicense took 260.7217254638672s
Availability | VoID file availability check for RDFLicense took 0.0005776882171630859s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.2642033100128174s
Reputation | Calculation of the PageRank for RDFLicense took 0.02086639404296875s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 4.267692565917969e-05s
Believability | Calculation of trust value for RDFLicense took 7.867813110351562e-06s
INFO | --- Analysis for rdflicense took 535.6909410953522s
Availability | SPARQL endpoint availability check for RDFohloh took 4.7206878662109375e-05s
Availability | VoID file availability check for RDFohloh took 0.0007207393646240234s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.27499890327453613s
Reputation | Calculation of the PageRank for RDFohloh took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for RDFohloh took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007548332214355469s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 9.250640869140625e-05s
Believability | Calculation of trust value for RDFohloh took 8.344650268554688e-06s
INFO | --- Analysis for rdfohloh took 7.861043691635132s
Availability | SPARQL endpoint availability check for Reactome RDF took 0.6509559154510498s
Availability | VoID file availability check for Reactome RDF took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.2950470447540283s
Reputation | Calculation of the PageRank for Reactome RDF took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.695487976074219e-05s
Believability | Calculation of trust value for Reactome RDF took 8.106231689453125e-06s
INFO | --- Analysis for reactome-rdf took 4.165475130081177s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 0.1873927116394043s
Availability | VoID file availability check for Rechtspraak.nl took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.2626016139984131s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020657777786254883s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.369850158691406e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 5.7220458984375e-06s
INFO | --- Analysis for rechtspraak took 3.07393479347229s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.5299530029296875e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2739686965942383s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.021237850189208984s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0010714530944824219s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 0.00010514259338378906s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 6.9141387939453125e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 7.572730541229248s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 0.05704331398010254s
Availability | VoID file availability check for reference.data.gov.uk took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2803075313568115s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007722377777099609s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015354156494140625s
Believability | Calculation of trust value for reference.data.gov.uk took 4.5299530029296875e-06s
INFO | --- Analysis for reference-data-gov-uk took 2.4909772872924805s
Availability | SPARQL endpoint availability check for Regiony took 4.076957702636719e-05s
Availability | VoID file availability check for Regiony took 0.00029015541076660156s
Completeness | Calculation of interlinking completeness for Regiony took 0.25980401039123535s
Reputation | Calculation of the PageRank for Regiony took 0.020409822463989258s
Interlinking | Calculation of Degree of Connection for Regiony took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Regiony took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Regiony took 2.8133392333984375e-05s
Believability | Calculation of trust value for Regiony took 6.9141387939453125e-06s
INFO | --- Analysis for regiony took 2.929422616958618s
Availability | SPARQL endpoint availability check for RELD took 261.5191419124603s
Availability | VoID file availability check for RELD took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for RELD took 0.27457380294799805s
Reputation | Calculation of the PageRank for RELD took 0.02121281623840332s
Interlinking | Calculation of Degree of Connection for RELD took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for RELD took 0.0009775161743164062s
Interlinking | Calculation of Clustering coefficient for RELD took 4.9114227294921875e-05s
Believability | Calculation of trust value for RELD took 8.106231689453125e-06s
INFO | --- Analysis for RELD took 536.2012920379639s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 0.2012619972229004s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0005056858062744141s
Extra | Recovery of all triples for Repository for Linked Open Archival Data took 1.5369157791137695s
Performance | Total latancy measurement for Repository for Linked Open Archival Data took 0.6562809944152832s
Amount of data | Number of triples check for Repository for Linked Open Archival Data took 1.4646368026733398s
Interoperability | New terms check for Repository for Linked Open Archival Data took 1.693699836730957s
Versatility | Languages check for Repository for Linked Open Archival Data took 6.681244611740112s
Interpretability | Number of blank nodes check for Repository for Linked Open Archival Data took 2.3596014976501465s
Security | Check HTTPS for Repository for Linked Open Archival Data took 0.22597789764404297s
Interpretability | RDF structures check for Repository for Linked Open Archival Data took 0.2971837520599365s
Versatility | Serialization formats check for Repository for Linked Open Archival Data took 0.34065866470336914s
Availability | RDF dump link check for Repository for Linked Open Archival Data took 0.18424487113952637s
License | MR license check for Repository for Linked Open Archival Data took 0.40726161003112793s
License | HR license check for Repository for Linked Open Archival Data took 8.427408218383789s
Amount of data | Number of property check for Repository for Linked Open Archival Data took 0.139570951461792s
Understandability | Number of label check for Repository for Linked Open Archival Data took 1.1224799156188965s
Understandability | URI regex check for Repository for Linked Open Archival Data took 0.42439889907836914s
Understandability | Vocabs check for Repository for Linked Open Archival Data took 0.1569652557373047s
Verifiability | Authors check for Repository for Linked Open Archival Data took 0.14688467979431152s
Verifiability | Publishers check for Repository for Linked Open Archival Data took 0.22810745239257812s
Performance | Throughput check for Repository for Linked Open Archival Data took 10.721001386642456s
Amount of data | Check the number of entities for Repository for Linked Open Archival Data took 0.00012731552124023438s
Verifiability | Contribs. check for Repository for Linked Open Archival Data took 0.09395837783813477s
Interlinking | sameAs chians check for Repository for Linked Open Archival Data took 0.21962547302246094s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.2896249294281006s
Interlinking | skos check for Repository for Linked Open Archival Data took 0.1371912956237793s
Timeliness | dataset update frequency check for Repository for Linked Open Archival Data took 0.30933356285095215s
Currency | Creation date check for Repository for Linked Open Archival Data took 0.28682661056518555s
Currency | Modification date check for Repository for Linked Open Archival Data took 0.26956772804260254s
Rep.Conc. | URIs length for Repository for Linked Open Archival Data took 3.1832780838012695s
Interoperability | New vocabularies check for Repository for Linked Open Archival Data took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Repository for Linked Open Archival Data took 0.17342638969421387s
Accuracy | Check Functional Property for Repository for Linked Open Archival Data took 0.12124896049499512s
Accuracy | Check Inverse Functional Property for Repository for Linked Open Archival Data took 0.15354132652282715s
Accuracy | Check Empty annotation labels for Repository for Linked Open Archival Data took 1.3307969570159912s
Accuracy | Check White space in annotation for Repository for Linked Open Archival Data took 0.029102802276611328s
Accuracy | Check Datatype consistency for Repository for Linked Open Archival Data took 0.028619766235351562s
Consistency | Disjoint class check for Repository for Linked Open Archival Data took 0.24296331405639648s
Consistency | Check Misplaced properties for Repository for Linked Open Archival Data took 2.1885132789611816s
Consistency | Misplaced classes for Repository for Linked Open Archival Data took 0.1741628646850586s
Consistency | Check Ontology hijacking for Repository for Linked Open Archival Data took 1.7587666511535645s
Consistency | Check Invalid usage of undefined classes for Repository for Linked Open Archival Data took 1.2914834022521973s
Consistency | Check Invalid usage of undefined properties for Repository for Linked Open Archival Data took 3.2859373092651367s
Conciseness | Check Extensional conciseness for Repository for Linked Open Archival Data took 0.029845476150512695s
Conciseness | Check Intensional conciseness for Repository for Linked Open Archival Data took 0.17435407638549805s
Security | Sign check for Repository for Linked Open Archival Data took 0.4952123165130615s
Availability | Check URIs Dereferenciability for Repository for Linked Open Archival Data took 1137.9852797985077s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 1.2809574604034424s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.020926475524902344s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 5.269050598144531e-05s
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 7.152557373046875e-06s
INFO | --- Analysis for reload took 1264.3159065246582s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.4345855712890625e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0006623268127441406s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.6921854019165039s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02053070068359375s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for Land use merced dataset took 9.298324584960938e-06s
INFO | --- Analysis for remote_Sensing took 14.03383469581604s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 1.92942214012146s
Availability | VoID file availability check for Renewable Energy Generators took 0.0006833076477050781s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.2749207019805908s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020637989044189453s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0008127689361572266s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.76837158203125e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 6.198883056640625e-06s
INFO | --- Analysis for renewable_energy_generators took 12.1234712600708s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 0.11720061302185059s
Availability | VoID file availability check for research.data.gov.uk took 0.0009124279022216797s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.22803473472595215s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 9.560585021972656e-05s
Believability | Calculation of trust value for research.data.gov.uk took 5.245208740234375e-06s
INFO | --- Analysis for research-data-gov-uk took 3.072279930114746s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.673004150390625e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0002281665802001953s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2540242671966553s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 2.86102294921875e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 6.67572021484375e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 3.3102712631225586s
Availability | SPARQL endpoint availability check for Restaurantes took 4.1484832763671875e-05s
Availability | VoID file availability check for Restaurantes took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.2945070266723633s
Reputation | Calculation of the PageRank for Restaurantes took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Restaurantes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.8848648071289062e-05s
Believability | Calculation of trust value for Restaurantes took 7.867813110351562e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.9600133895874023s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.2438507080078125e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.0005571842193603516s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.2831156253814697s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007803440093994141s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 7.05718994140625e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 6.198883056640625e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 4.034166574478149s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 0.042385101318359375s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.24124789237976074s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.075599670410156e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 6.4373016357421875e-06s
INFO | --- Analysis for revistas_turismo took 2.4178719520568848s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 0.26001787185668945s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2523651123046875s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011777877807617188s
Believability | Calculation of trust value for Revyu.com - Review Anything took 7.62939453125e-06s
INFO | --- Analysis for revyu took 2.5807182788848877s
Availability | SPARQL endpoint availability check for sdafsadf took 0.35417723655700684s
Availability | VoID file availability check for sdafsadf took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.2835259437561035s
Reputation | Calculation of the PageRank for sdafsadf took 0.02027440071105957s
Interlinking | Calculation of Degree of Connection for sdafsadf took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.8371810913085938e-05s
Believability | Calculation of trust value for sdafsadf took 6.9141387939453125e-06s
INFO | --- Analysis for rgsdfg took 3.2261300086975098s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.363059997558594e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.260880708694458s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 5.125999450683594e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.7404556274414062e-05s
INFO | --- Analysis for riese took 2.443138360977173s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 4.100799560546875e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.2533860206604004s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020633459091186523s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 6.9141387939453125e-06s
INFO | --- Analysis for rijksmuseum took 2.8871121406555176s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 0.6536593437194824s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0006062984466552734s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.2827334403991699s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.02046799659729004s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.291534423828125e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 7.3909759521484375e-06s
INFO | --- Analysis for rism took 3.5874414443969727s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.17905163764953613s
Availability | VoID file availability check for RISM Authority data took 0.0007061958312988281s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.26740455627441406s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.38690185546875e-05s
Believability | Calculation of trust value for RISM Authority data took 7.152557373046875e-06s
INFO | --- Analysis for rism-authorities took 3.1400580406188965s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.2513427734375s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for engineering equipment ontology took 6.9141387939453125e-06s
INFO | --- Analysis for rk took 2.3603179454803467s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.04475569725036621s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.26009488105773926s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.021524667739868164s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0009708404541015625s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0002760887145996094s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.428598165512085s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.049556732177734375s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.25745272636413574s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.00014138221740722656s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.437915325164795s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 0.051908016204833984s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.2566354274749756s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02028203010559082s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00019884109497070312s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 3.62396240234375e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 2.5021169185638428s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.04369187355041504s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.25731945037841797s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020302534103393555s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00016546249389648438s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.6676506996154785s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 0.03739643096923828s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.26934266090393066s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.020070791244506836s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00016069412231445312s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.4238357543945312s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 0.04649782180786133s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.271392822265625s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.6716461181640625e-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.5074994564056396s
Availability | SPARQL endpoint availability check for crm took 4.673004150390625e-05s
Availability | VoID file availability check for crm took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for crm took 0.2591969966888428s
Reputation | Calculation of the PageRank for crm took 0.020481348037719727s
Interlinking | Calculation of Degree of Connection for crm took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for crm took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for crm took 2.956390380859375e-05s
Believability | Calculation of trust value for crm took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-crm took 2.969980478286743s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.046256303787231445s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00042247772216796875s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.26500821113586426s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00012087821960449219s
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.435178518295288s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 0.04573321342468262s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.24589300155639648s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007517337799072266s
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.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.3694045543670654s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.04719281196594238s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.25647759437561035s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002396106719970703s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.4644391536712646s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 0.03735542297363281s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2365734577178955s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.62939453125e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.467933416366577s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 0.05119752883911133s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.26242661476135254s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.751319885253906e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.4743852615356445s
Availability | SPARQL endpoint availability check for digitaleconomy took 0.04326343536376953s
Availability | VoID file availability check for digitaleconomy took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.27301740646362305s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.147125244140625e-05s
Believability | Calculation of trust value for digitaleconomy took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.4947896003723145s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 0.08401894569396973s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.2656223773956299s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014972686767578125s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.4262378215789795s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 0.037071943283081055s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.2530221939086914s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020988941192626953s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.601478576660156e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-ecs took 2.7982072830200195s
Availability | SPARQL endpoint availability check for enaktingpsi took 4.124641418457031e-05s
Availability | VoID file availability check for enaktingpsi took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.24183344841003418s
Reputation | Calculation of the PageRank for enaktingpsi took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.000827789306640625s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 3.361701965332031e-05s
Believability | Calculation of trust value for enaktingpsi took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.847209930419922s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.04687786102294922s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.25843143463134766s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.023357868194580078s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0012960433959960938s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00026488304138183594s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.5169363021850586s
Availability | SPARQL endpoint availability check for epsrc took 0.047441959381103516s
Availability | VoID file availability check for epsrc took 0.000347137451171875s
Completeness | Calculation of interlinking completeness for epsrc took 0.2718324661254883s
Reputation | Calculation of the PageRank for epsrc took 0.020391464233398438s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.7220458984375e-05s
Believability | Calculation of trust value for epsrc took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.462083578109741s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.048120975494384766s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.25713133811950684s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020853519439697266s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.535385131835938e-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.4521842002868652s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.052414894104003906s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.2662646770477295s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007538795471191406s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010204315185546875s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.4527790546417236s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.100799560546875e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.26213741302490234s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.02019333839416504s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 2.86102294921875e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-foreign took 2.908504009246826s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.042420387268066406s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.25895142555236816s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.020364999771118164s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.869171142578125e-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.442354440689087s
Availability | SPARQL endpoint availability check for fun took 0.04122042655944824s
Availability | VoID file availability check for fun took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for fun took 0.24147367477416992s
Reputation | Calculation of the PageRank for fun took 0.02022838592529297s
Interlinking | Calculation of Degree of Connection for fun took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for fun took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for fun took 7.390975952148438e-05s
Believability | Calculation of trust value for fun took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.4325177669525146s
Availability | SPARQL endpoint availability check for gdlc took 0.0411837100982666s
Availability | VoID file availability check for gdlc took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for gdlc took 0.2594311237335205s
Reputation | Calculation of the PageRank for gdlc took 0.021581411361694336s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0008916854858398438s
Interlinking | Calculation of Clustering coefficient for gdlc took 8.511543273925781e-05s
Believability | Calculation of trust value for gdlc took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.4174420833587646s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 0.05493879318237305s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.25897979736328125s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011491775512695312s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.55157732963562s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 0.04062175750732422s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.26868271827697754s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020460844039916992s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001380443572998047s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.387181282043457s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.047969818115234375s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2612433433532715s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.02038288116455078s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00014162063598632812s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-irit took 2.439558506011963s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.043431758880615234s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.2698202133178711s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.604194641113281e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-italy took 2.477022647857666s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 0.03336977958679199s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.28368377685546875s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02060866355895996s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.62939453125e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.478031635284424s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.044381141662597656s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2839047908782959s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0203249454498291s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.267692565917969e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.488995313644409s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.04384660720825195s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2561459541320801s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0001659393310546875s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.4830424785614014s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.04183840751647949s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2401561737060547s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020357847213745117s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.00015020370483398438s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.4469492435455322s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.04148674011230469s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.26387524604797363s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.580352783203125e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.466304302215576s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.03887033462524414s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.2472233772277832s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020940303802490234s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.00016760826110839844s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-newcastle took 2.4893548488616943s
Availability | SPARQL endpoint availability check for notube took 0.034369707107543945s
Availability | VoID file availability check for notube took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for notube took 0.2743101119995117s
Reputation | Calculation of the PageRank for notube took 0.020143508911132812s
Interlinking | Calculation of Degree of Connection for notube took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for notube took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for notube took 4.172325134277344e-05s
Believability | Calculation of trust value for notube took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.409942865371704s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 0.04439067840576172s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.283447265625s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020438432693481445s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007579326629638672s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00013327598571777344s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-nsf took 2.4434144496917725s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.04579305648803711s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.26978588104248047s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00023484230041503906s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.49428129196167s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.315376281738281e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.252457857131958s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0008604526519775391s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 3.314018249511719e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.877103090286255s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 0.039115190505981445s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.2762126922607422s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02041029930114746s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.319450378417969e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 8.821487426757812e-06s
INFO | --- Analysis for rkb-explorer-os took 2.4822027683258057s
Availability | SPARQL endpoint availability check for photos took 0.04633808135986328s
Availability | VoID file availability check for photos took 0.0003647804260253906s
Completeness | Calculation of interlinking completeness for photos took 0.2579216957092285s
Reputation | Calculation of the PageRank for photos took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for photos took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for photos took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for photos took 7.152557373046875e-05s
Believability | Calculation of trust value for photos took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.3982534408569336s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 0.04215097427368164s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.24973511695861816s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02018904685974121s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.0001125335693359375s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.4221227169036865s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.04557299613952637s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.2757835388183594s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019049644470214844s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.4641287326812744s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.04137015342712402s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.27420568466186523s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00014162063598632812s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.507946491241455s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 0.04182553291320801s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.25564146041870117s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.036064147949219e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.4828476905822754s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.04256272315979004s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.24892950057983398s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020296573638916016s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00013136863708496094s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.419646978378296s
Availability | SPARQL endpoint availability check for roni took 0.04088449478149414s
Availability | VoID file availability check for roni took 0.00042724609375s
Completeness | Calculation of interlinking completeness for roni took 0.2745695114135742s
Reputation | Calculation of the PageRank for roni took 0.020398616790771484s
Interlinking | Calculation of Degree of Connection for roni took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for roni took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for roni took 2.8133392333984375e-05s
Believability | Calculation of trust value for roni took 6.4373016357421875e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.4676921367645264s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0421910285949707s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.2752096652984619s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.023027896881103516s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0010876655578613281s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00028443336486816406s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.457794189453125s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 0.04253220558166504s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.24640536308288574s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020995378494262695s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00011348724365234375s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.451070547103882s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 0.04851651191711426s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.26113367080688477s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.846687316894531e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.4315571784973145s
Availability | SPARQL endpoint availability check for webconf took 0.049166202545166016s
Availability | VoID file availability check for webconf took 0.0005025863647460938s
Completeness | Calculation of interlinking completeness for webconf took 0.25583362579345703s
Reputation | Calculation of the PageRank for webconf took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for webconf took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for webconf took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for webconf took 0.0001068115234375s
Believability | Calculation of trust value for webconf took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-webconf took 13.038965463638306s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 0.03753042221069336s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.25869035720825195s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.867813110351562e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.478454113006592s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 0.042093753814697266s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.25991129875183105s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00020265579223632812s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.5322952270507812s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 0.04377460479736328s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.2708122730255127s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0010271072387695312s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 0.00011420249938964844s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.4406955242156982s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.291534423828125e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.25555920600891113s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.152557373046875e-06s
INFO | --- Analysis for rkb_explorer_data took 2.8662476539611816s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.4934117794036865s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.26168084144592285s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02056598663330078s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 7.867813110351562e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 6.67572021484375e-06s
INFO | --- Analysis for roceeh-road took 3.6320464611053467s
Availability | SPARQL endpoint availability check for The Rosetta Project took 5.459785461425781e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2530531883239746s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 2.7418136596679688e-05s
Believability | Calculation of trust value for The Rosetta Project took 7.152557373046875e-06s
INFO | --- Analysis for rosetta-project took 2.970872640609741s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.8160552978515625e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0006785392761230469s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.2879753112792969s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020088911056518555s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.7418136596679688e-05s
Believability | Calculation of trust value for ontology terrorist attack took 6.67572021484375e-06s
INFO | --- Analysis for ROSHANI took 3.5715670585632324s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.3392181396484375e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.2643144130706787s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.24249267578125e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 7.3909759521484375e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.4015023708343506s
Availability | SPARQL endpoint availability check for x took 4.363059997558594e-05s
Availability | VoID file availability check for x took 0.0006859302520751953s
Completeness | Calculation of interlinking completeness for x took 0.2789750099182129s
Reputation | Calculation of the PageRank for x took 0.02072763442993164s
Interlinking | Calculation of Degree of Connection for x took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for x took 0.0008375644683837891s
Interlinking | Calculation of Clustering coefficient for x took 3.361701965332031e-05s
Believability | Calculation of trust value for x took 7.152557373046875e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.377211570739746s
Availability | SPARQL endpoint availability check for Rpm Find took 4.1484832763671875e-05s
Availability | VoID file availability check for Rpm Find took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.277787446975708s
Reputation | Calculation of the PageRank for Rpm Find took 0.020418167114257812s
Interlinking | Calculation of Degree of Connection for Rpm Find took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 2.8848648071289062e-05s
Believability | Calculation of trust value for Rpm Find took 6.67572021484375e-06s
INFO | --- Analysis for rpm_find took 2.93143892288208s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 6.580352783203125e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0005860328674316406s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.261563777923584s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.020285367965698242s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.747245788574219e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 7.62939453125e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 3.6469180583953857s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 6.580352783203125e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0005788803100585938s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.266448974609375s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.02038741111755371s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0007729530334472656s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 8.058547973632812e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 7.62939453125e-06s
INFO | --- Analysis for rubentaelman took 2.8231992721557617s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 4.291534423828125e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.2715303897857666s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020314931869506836s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 0.00010752677917480469s
Believability | Calculation of trust value for Ruben Verborgh's data took 1.1920928955078125e-05s
INFO | --- Analysis for rubenverborgh took 3.2952306270599365s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 393.24642872810364s
Availability | VoID file availability check for Russian Universities Specialities took 0.0006649494171142578s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.6808037757873535s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 4.506111145019531e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 7.152557373046875e-06s
INFO | --- Analysis for russian-universities-specialities took 678.4867625236511s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.482269287109375e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.7017261981964111s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020719528198242188s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0009868144989013672s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 4.839897155761719e-05s
Believability | Calculation of trust value for RuThes Cloud took 7.152557373046875e-06s
INFO | --- Analysis for ruthes took 5.178483724594116s
Availability | SPARQL endpoint availability check for RxNorm took 4.172325134277344e-05s
Availability | VoID file availability check for RxNorm took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for RxNorm took 0.2661013603210449s
Reputation | Calculation of the PageRank for RxNorm took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.457069396972656e-05s
Believability | Calculation of trust value for RxNorm took 7.62939453125e-06s
INFO | --- Analysis for rxnorm took 4.256061792373657s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 6.912710905075073s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.27605414390563965s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.020439624786376953s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 2.956390380859375e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 7.152557373046875e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 12.633577823638916s
Availability | SPARQL endpoint availability check for SALDO took 4.1484832763671875e-05s
Availability | VoID file availability check for SALDO took 0.000244140625s
Completeness | Calculation of interlinking completeness for SALDO took 0.27441930770874023s
Reputation | Calculation of the PageRank for SALDO took 0.020263671875s
Interlinking | Calculation of Degree of Connection for SALDO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SALDO took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for SALDO took 2.9087066650390625e-05s
Believability | Calculation of trust value for SALDO took 7.62939453125e-06s
INFO | --- Analysis for saldo took 2.940889596939087s
Availability | SPARQL endpoint availability check for SALDO-RDF took 1.3211402893066406s
Availability | VoID file availability check for SALDO-RDF took 0.0006906986236572266s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.25734424591064453s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007488727569580078s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for SALDO-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for saldo-rdf took 5.818859577178955s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 0.6616675853729248s
Availability | VoID file availability check for SALDOM-RDF took 0.0006866455078125s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.2670717239379883s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.5762786865234375e-05s
Believability | Calculation of trust value for SALDOM-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for saldom-rdf took 4.781976938247681s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.410743713378906e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2733132839202881s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02051067352294922s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010967254638671875s
Believability | Calculation of trust value for Salzburgerland DE took 7.867813110351562e-06s
INFO | --- Analysis for salzburgerland-com-de took 3.057596206665039s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.291534423828125e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.26789379119873047s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0007836818695068359s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.0001049041748046875s
Believability | Calculation of trust value for Salzburgerland EN took 8.106231689453125e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.8423843383789062s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.9114227294921875e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.2619774341583252s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010561943054199219s
Believability | Calculation of trust value for Salzburgerland IT took 7.62939453125e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.9162867069244385s
Availability | SPARQL endpoint availability check for sameAs.org took 4.124641418457031e-05s
Availability | VoID file availability check for sameAs.org took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.27989959716796875s
Reputation | Calculation of the PageRank for sameAs.org took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for sameAs.org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.8848648071289062e-05s
Believability | Calculation of trust value for sameAs.org took 7.62939453125e-06s
INFO | --- Analysis for sameas-org took 2.969667673110962s
Availability | SPARQL endpoint availability check for sandrart.net took 7.867813110351562e-05s
Availability | VoID file availability check for sandrart.net took 0.0003972053527832031s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.24999713897705078s
Reputation | Calculation of the PageRank for sandrart.net took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for sandrart.net took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.842613220214844e-05s
Believability | Calculation of trust value for sandrart.net took 7.62939453125e-06s
INFO | --- Analysis for sandrart-net took 3.49505352973938s
Availability | SPARQL endpoint availability check for Taxons  took 1.0870351791381836s
Availability | VoID file availability check for Taxons  took 0.0004487037658691406s
Extra | Recovery of all triples for Taxons  took 26.646334409713745s
Performance | Total latancy measurement for Taxons  took 0.4214465618133545s
Amount of data | Number of triples check for Taxons  took 2.2762715816497803s
Interoperability | New terms check for Taxons  took 2.5287420749664307s
Versatility | Languages check for Taxons  took 39.115418910980225s
Interpretability | Number of blank nodes check for Taxons  took 1.184593677520752s
Security | Check HTTPS for Taxons  took 0.20166945457458496s
Interpretability | RDF structures check for Taxons  took 1.5125203132629395s
Versatility | Serialization formats check for Taxons  took 0.728548526763916s
Availability | RDF dump link check for Taxons  took 0.2757549285888672s
License | MR license check for Taxons  took 1.701328992843628s
License | HR license check for Taxons  took 2.64731764793396s
Amount of data | Number of property check for Taxons  took 0.22609567642211914s
Understandability | Number of label check for Taxons  took 2.7963080406188965s
Understandability | URI regex check for Taxons  took 0.6952581405639648s
Understandability | Vocabs check for Taxons  took 0.1995103359222412s
Verifiability | Authors check for Taxons  took 0.1172475814819336s
Verifiability | Publishers check for Taxons  took 0.0875859260559082s
Performance | Throughput check for Taxons  took 10.52271318435669s
Amount of data | Check the number of entities for Taxons  took 7.295608520507812e-05s
Verifiability | Contribs. check for Taxons  took 0.08971428871154785s
Interlinking | sameAs chians check for Taxons  took 0.16909074783325195s
Interlinking | skos check for Taxons  took 0.15700483322143555s
Interlinking | skos check for Taxons  took 0.09731197357177734s
Timeliness | dataset update frequency check for Taxons  took 0.5836086273193359s
Currency | Creation date check for Taxons  took 0.2023451328277588s
Currency | Modification date check for Taxons  took 0.26146483421325684s
Rep.Conc. | URIs length for Taxons  took 26.17526340484619s
Interoperability | New vocabularies check for Taxons  took 6.9141387939453125e-06s
Consistency | Deprecated classes/propertiers check for Taxons  took 0.10542774200439453s
Accuracy | Check Functional Property for Taxons  took 0.46760988235473633s
Accuracy | Check Inverse Functional Property for Taxons  took 0.4358248710632324s
Accuracy | Check Empty annotation labels for Taxons  took 7.467528343200684s
Accuracy | Check White space in annotation for Taxons  took 0.30597472190856934s
Accuracy | Check Datatype consistency for Taxons  took 0.2628469467163086s
Consistency | Disjoint class check for Taxons  took 0.12885522842407227s
Consistency | Check Misplaced properties for Taxons  took 4.2801103591918945s
Consistency | Misplaced classes for Taxons  took 0.9587037563323975s
Consistency | Check Ontology hijacking for Taxons  took 5.512258052825928s
Consistency | Check Invalid usage of undefined classes for Taxons  took 1.3326520919799805s
Consistency | Check Invalid usage of undefined properties for Taxons  took 5.442917346954346s
Conciseness | Check Extensional conciseness for Taxons  took 0.2909872531890869s
Conciseness | Check Intensional conciseness for Taxons  took 0.17745351791381836s
Security | Sign check for Taxons  took 0.9671566486358643s
Availability | Check URIs Dereferenciability for Taxons  took 1658.2310514450073s
Completeness | Calculation of interlinking completeness for Taxons  took 1.4332504272460938s
Reputation | Calculation of the PageRank for Taxons  took 0.020992517471313477s
Interlinking | Calculation of Degree of Connection for Taxons  took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Taxons  took 7.581710815429688e-05s
Interoperability | Check the re-using of existing vocabs for Taxons  took 2.1457672119140625e-06s
Believability | Calculation of trust value for Taxons  took 1.3589859008789062e-05s
INFO | --- Analysis for sandre took 1877.0483856201172s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 1.8340568542480469s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.7284789085388184s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02083873748779297s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0007941722869873047s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 4.0531158447265625e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.71661376953125e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 8.270819902420044s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 263.8188934326172s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0007655620574951172s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.2860844135284424s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.020790815353393555s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.8623809814453125e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 7.62939453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 668.984715461731s
Availability | SPARQL endpoint availability check for SATAR test  took 4.38690185546875e-05s
Availability | VoID file availability check for SATAR test  took 0.0007512569427490234s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.2917025089263916s
Reputation | Calculation of the PageRank for SATAR test  took 0.021060943603515625s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.361701965332031e-05s
Believability | Calculation of trust value for SATAR test  took 6.67572021484375e-06s
INFO | --- Analysis for SATAR_test took 5.227823495864868s
Availability | SPARQL endpoint availability check for SCBG Data took 21.602901458740234s
Availability | VoID file availability check for SCBG Data took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.6847009658813477s
Reputation | Calculation of the PageRank for SCBG Data took 0.020726442337036133s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.249282836914062e-05s
Believability | Calculation of trust value for SCBG Data took 7.3909759521484375e-06s
INFO | --- Analysis for SCBG-Data took 54.42266488075256s
Availability | SPARQL endpoint availability check for schema.org took 5.316734313964844e-05s
Availability | VoID file availability check for schema.org took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for schema.org took 0.24837350845336914s
Reputation | Calculation of the PageRank for schema.org took 0.020618677139282227s
Interlinking | Calculation of Degree of Connection for schema.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for schema.org took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.695487976074219e-05s
Believability | Calculation of trust value for schema.org took 7.152557373046875e-06s
INFO | --- Analysis for schema-org took 4.641531229019165s
Availability | SPARQL endpoint availability check for Schemantra took 4.363059997558594e-05s
Availability | VoID file availability check for Schemantra took 0.00022649765014648438s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2786824703216553s
Reputation | Calculation of the PageRank for Schemantra took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for Schemantra took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Schemantra took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.314018249511719e-05s
Believability | Calculation of trust value for Schemantra took 6.4373016357421875e-06s
INFO | --- Analysis for Schemantra took 2.3621363639831543s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 1.884355068206787s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0006959438323974609s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.25964975357055664s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.6716461181640625e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 7.3909759521484375e-06s
INFO | --- Analysis for schemapedia took 5.108804225921631s
Availability | SPARQL endpoint availability check for scholarlydata took 4.100799560546875e-05s
Availability | VoID file availability check for scholarlydata took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.2615177631378174s
Reputation | Calculation of the PageRank for scholarlydata took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for scholarlydata took 4.8160552978515625e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 3.24249267578125e-05s
Believability | Calculation of trust value for scholarlydata took 6.9141387939453125e-06s
INFO | --- Analysis for scholarlydata took 2.947383165359497s
Availability | SPARQL endpoint availability check for Scholarometer took 4.2438507080078125e-05s
Availability | VoID file availability check for Scholarometer took 0.0006580352783203125s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.2748100757598877s
Reputation | Calculation of the PageRank for Scholarometer took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.869171142578125e-05s
Believability | Calculation of trust value for Scholarometer took 5.7220458984375e-06s
INFO | --- Analysis for scholarometer took 7.039072513580322s
Availability | SPARQL endpoint availability check for Science Commons took 4.267692565917969e-05s
Availability | VoID file availability check for Science Commons took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Science Commons took 0.29535531997680664s
Reputation | Calculation of the PageRank for Science Commons took 0.020638465881347656s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.123283386230469e-05s
Believability | Calculation of trust value for Science Commons took 6.67572021484375e-06s
INFO | --- Analysis for science_commons took 3.442434310913086s
Availability | SPARQL endpoint availability check for ScienceWise took 4.3392181396484375e-05s
Availability | VoID file availability check for ScienceWise took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2672879695892334s
Reputation | Calculation of the PageRank for ScienceWise took 0.02020573616027832s
Interlinking | Calculation of Degree of Connection for ScienceWise took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.0994415283203125e-05s
Believability | Calculation of trust value for ScienceWise took 6.4373016357421875e-06s
INFO | --- Analysis for sciencewise took 2.8883345127105713s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.4345855712890625e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2802588939666748s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020499229431152344s
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.0007476806640625s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 3.0040740966796875e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 5.0067901611328125e-06s
INFO | --- Analysis for scoreboard took 4.6770079135894775s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.291534423828125e-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.0006389617919921875s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.2484269142150879s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0206606388092041s
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.298324584960938e-06s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 3.695487976074219e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 7.152557373046875e-06s
INFO | --- Analysis for SDDEC took 17.302057027816772s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.410743713378906e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007786750793457031s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.26828789710998535s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0205991268157959s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007977485656738281s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.00543212890625e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.3909759521484375e-06s
INFO | --- Analysis for SDG took 3.348843812942505s
Availability | SPARQL endpoint availability check for sears.com took 4.4345855712890625e-05s
Availability | VoID file availability check for sears.com took 0.0007257461547851562s
Completeness | Calculation of interlinking completeness for sears.com took 0.26313233375549316s
Reputation | Calculation of the PageRank for sears.com took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for sears.com took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for sears.com took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.67572021484375e-05s
Believability | Calculation of trust value for sears.com took 6.4373016357421875e-06s
INFO | --- Analysis for sears took 4.416433572769165s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.07193684577941895s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0006780624389648438s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.2692134380340576s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.02029109001159668s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.511543273925781e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 5.245208740234375e-06s
INFO | --- Analysis for sec-rdfabout took 35.83551859855652s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 31.7339825630188s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.001386404037475586s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.28392529487609863s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 0.00010848045349121094s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for secold took 167.77637243270874s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.267692565917969e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.27185821533203125s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 3.170967102050781e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 9.298324584960938e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 2.909965753555298s
Availability | SPARQL endpoint availability check for semanlink took 4.410743713378906e-05s
Availability | VoID file availability check for semanlink took 0.0009613037109375s
Completeness | Calculation of interlinking completeness for semanlink took 0.2422342300415039s
Reputation | Calculation of the PageRank for semanlink took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.000141143798828125s
Believability | Calculation of trust value for semanlink took 6.4373016357421875e-06s
INFO | --- Analysis for semanlink took 183.17155838012695s
Availability | SPARQL endpoint availability check for Semantic Library took 6.127357482910156e-05s
Availability | VoID file availability check for Semantic Library took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2546050548553467s
Reputation | Calculation of the PageRank for Semantic Library took 0.020277976989746094s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.123283386230469e-05s
Believability | Calculation of trust value for Semantic Library took 6.9141387939453125e-06s
INFO | --- Analysis for semantic-library took 2.8157687187194824s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.2605092525482178s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020567655563354492s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0008192062377929688s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.0994415283203125e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 6.67572021484375e-06s
INFO | --- Analysis for semantic-profiling-network took 2.9169058799743652s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 0.06123232841491699s
Availability | VoID file availability check for Semantic Universe Data took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.27370405197143555s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.337860107421875e-05s
Believability | Calculation of trust value for Semantic Universe Data took 7.62939453125e-06s
INFO | --- Analysis for semantic-universe took 2.5084095001220703s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 30.351380825042725s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.0006582736968994141s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.24176526069641113s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.02066493034362793s
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.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011515617370605469s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 8.344650268554688e-06s
INFO | --- Analysis for semantic-web-dog-food took 83.2856228351593s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 4.363059997558594e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.25893378257751465s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.02039361000061035s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 5.125999450683594e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 7.152557373046875e-06s
INFO | --- Analysis for semantic-web-grundlagen took 3.4623820781707764s
Availability | SPARQL endpoint availability check for semantic-web-journal took 8.416175842285156e-05s
Availability | VoID file availability check for semantic-web-journal took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.24642086029052734s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.020464181900024414s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 2.956390380859375e-05s
Believability | Calculation of trust value for semantic-web-journal took 6.9141387939453125e-06s
INFO | --- Analysis for semantic-web-journal took 2.8815388679504395s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.57763671875e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0006182193756103516s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2797086238861084s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.368492126464844e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 5.245208740234375e-06s
INFO | --- Analysis for semantic-xbrl took 3.3919334411621094s
Availability | SPARQL endpoint availability check for Semantic Bible took 5.6743621826171875e-05s
Availability | VoID file availability check for Semantic Bible took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2821009159088135s
Reputation | Calculation of the PageRank for Semantic Bible took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.314018249511719e-05s
Believability | Calculation of trust value for Semantic Bible took 8.344650268554688e-06s
INFO | --- Analysis for semantic_bible took 2.9507057666778564s
Availability | SPARQL endpoint availability check for SemanticQuran took 6.984473705291748s
Availability | VoID file availability check for SemanticQuran took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.2836644649505615s
Reputation | Calculation of the PageRank for SemanticQuran took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 7.2479248046875e-05s
Believability | Calculation of trust value for SemanticQuran took 7.62939453125e-06s
INFO | --- Analysis for semanticquran took 16.032832384109497s
Availability | SPARQL endpoint availability check for SemanticTweet took 5.507469177246094e-05s
Availability | VoID file availability check for SemanticTweet took 0.000621795654296875s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.2582428455352783s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.412101745605469e-05s
Believability | Calculation of trust value for SemanticTweet took 7.867813110351562e-06s
INFO | --- Analysis for semantictweet took 4.153028726577759s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.601478576660156e-05s
Availability | VoID file availability check for semanticweb.org took 0.0006427764892578125s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.27234506607055664s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020555734634399414s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.796287536621094e-05s
Believability | Calculation of trust value for semanticweb.org took 1.239776611328125e-05s
INFO | --- Analysis for semanticweb-org took 22.648521423339844s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.08869242668151855s
Availability | VoID file availability check for Semantic CrunchBase took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.2569124698638916s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.02046966552734375s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.62939453125e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.3828277587890625e-05s
INFO | --- Analysis for semsol-crunchbase took 2.495124578475952s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 4.935264587402344e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.25296831130981445s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 3.1948089599609375e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.106231689453125e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.878962755203247s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 0.259929895401001s
Availability | VoID file availability check for SentimentWortschatz took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.24616694450378418s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02012324333190918s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.000732421875s
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.506856679916382s
Availability | SPARQL endpoint availability check for seoul-bike-data took 30.101972818374634s
Availability | VoID file availability check for seoul-bike-data took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.4093952178955078s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 2.956390380859375e-05s
Believability | Calculation of trust value for seoul-bike-data took 7.3909759521484375e-06s
INFO | --- Analysis for seoul-bike-data took 72.83489060401917s
Availability | SPARQL endpoint availability check for Serendipity took 8.196646451950073s
Availability | VoID file availability check for Serendipity took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for Serendipity took 0.27149462699890137s
Reputation | Calculation of the PageRank for Serendipity took 0.020253896713256836s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.00072479248046875s
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 15.80644154548645s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 7.2479248046875e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.28129124641418457s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007562637329101562s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.552436828613281e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 7.62939453125e-06s
INFO | --- Analysis for Sherry_Wine took 3.0741732120513916s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.458427429199219e-05s
Availability | VoID file availability check for Sherry Wine took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.28293681144714355s
Reputation | Calculation of the PageRank for Sherry Wine took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.075599670410156e-05s
Believability | Calculation of trust value for Sherry Wine took 5.7220458984375e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.3989815711975098s
Availability | SPARQL endpoint availability check for Shoah victims? names took 0.2197270393371582s
Availability | VoID file availability check for Shoah victims? names took 0.0005154609680175781s
Extra | Recovery of all triples for Shoah victims? names took 1.523977279663086s
Performance | Total latancy measurement for Shoah victims? names took 0.6675236225128174s
Amount of data | Number of triples check for Shoah victims? names took 1.317591667175293s
Interoperability | New terms check for Shoah victims? names took 1.7582077980041504s
Versatility | Languages check for Shoah victims? names took 6.095580816268921s
Interpretability | Number of blank nodes check for Shoah victims? names took 2.524599075317383s
Security | Check HTTPS for Shoah victims? names took 0.24343109130859375s
Interpretability | RDF structures check for Shoah victims? names took 0.26465320587158203s
Versatility | Serialization formats check for Shoah victims? names took 0.4499678611755371s
Availability | RDF dump link check for Shoah victims? names took 0.23243474960327148s
License | MR license check for Shoah victims? names took 0.34894824028015137s
License | HR license check for Shoah victims? names took 7.834495306015015s
Amount of data | Number of property check for Shoah victims? names took 0.19981861114501953s
Understandability | Number of label check for Shoah victims? names took 1.0643353462219238s
Understandability | URI regex check for Shoah victims? names took 0.5756101608276367s
Understandability | Vocabs check for Shoah victims? names took 0.19985580444335938s
Verifiability | Authors check for Shoah victims? names took 0.23844623565673828s
Verifiability | Publishers check for Shoah victims? names took 0.21495914459228516s
Performance | Throughput check for Shoah victims? names took 10.339492559432983s
Amount of data | Check the number of entities for Shoah victims? names took 7.367134094238281e-05s
Verifiability | Contribs. check for Shoah victims? names took 0.27778124809265137s
Interlinking | sameAs chians check for Shoah victims? names took 0.14911222457885742s
Interlinking | skos check for Shoah victims? names took 0.21898603439331055s
Interlinking | skos check for Shoah victims? names took 0.07216215133666992s
Timeliness | dataset update frequency check for Shoah victims? names took 0.2148141860961914s
Currency | Creation date check for Shoah victims? names took 0.2732431888580322s
Currency | Modification date check for Shoah victims? names took 0.35354113578796387s
Rep.Conc. | URIs length for Shoah victims? names took 2.7994613647460938s
Interoperability | New vocabularies check for Shoah victims? names took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for Shoah victims? names took 0.17049741744995117s
Accuracy | Check Functional Property for Shoah victims? names took 0.11497879028320312s
Accuracy | Check Inverse Functional Property for Shoah victims? names took 0.1554851531982422s
Accuracy | Check Empty annotation labels for Shoah victims? names took 0.7969839572906494s
Accuracy | Check White space in annotation for Shoah victims? names took 0.028996944427490234s
Accuracy | Check Datatype consistency for Shoah victims? names took 0.027842283248901367s
Consistency | Disjoint class check for Shoah victims? names took 0.24132537841796875s
Consistency | Check Misplaced properties for Shoah victims? names took 1.8477632999420166s
Consistency | Misplaced classes for Shoah victims? names took 0.24787664413452148s
Consistency | Check Ontology hijacking for Shoah victims? names took 1.8211839199066162s
Consistency | Check Invalid usage of undefined classes for Shoah victims? names took 1.2805674076080322s
Consistency | Check Invalid usage of undefined properties for Shoah victims? names took 3.0219032764434814s
Conciseness | Check Extensional conciseness for Shoah victims? names took 0.02983260154724121s
Conciseness | Check Intensional conciseness for Shoah victims? names took 0.15376591682434082s
Security | Sign check for Shoah victims? names took 0.5341346263885498s
Availability | Check URIs Dereferenciability for Shoah victims? names took 1146.7424557209015s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 1.1207592487335205s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.02070140838623047s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 3.7670135498046875e-05s
Interoperability | Check the re-using of existing vocabs for Shoah victims? names took 1.9073486328125e-06s
Believability | Calculation of trust value for Shoah victims? names took 8.58306884765625e-06s
INFO | --- Analysis for shoah-victims-names took 1255.2981369495392s
Availability | SPARQL endpoint availability check for Person took 4.696846008300781e-05s
Availability | VoID file availability check for Person took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Person took 0.2792394161224365s
Reputation | Calculation of the PageRank for Person took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Person took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Person took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for Person took 3.123283386230469e-05s
Believability | Calculation of trust value for Person took 7.152557373046875e-06s
INFO | --- Analysis for Shripriya_Dubey took 3.2540924549102783s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.38690185546875e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.26644206047058105s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020262718200683594s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 8.106231689453125e-06s
INFO | --- Analysis for Shutterstock took 2.820897102355957s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.076957702636719e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.27188658714294434s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.123283386230469e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 1.1444091796875e-05s
INFO | --- Analysis for simile_data_collection took 3.0005149841308594s
Availability | SPARQL endpoint availability check for SIMPLE took 4.5299530029296875e-05s
Availability | VoID file availability check for SIMPLE took 0.0006437301635742188s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.26399731636047363s
Reputation | Calculation of the PageRank for SIMPLE took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.076957702636719e-05s
Believability | Calculation of trust value for SIMPLE took 7.867813110351562e-06s
INFO | --- Analysis for simple took 5.333883047103882s
Availability | SPARQL endpoint availability check for SITC-V4 took 25.53330969810486s
Availability | VoID file availability check for SITC-V4 took 0.0007467269897460938s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.2610204219818115s
Reputation | Calculation of the PageRank for SITC-V4 took 0.02158498764038086s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007684230804443359s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 4.1484832763671875e-05s
Believability | Calculation of trust value for SITC-V4 took 5.0067901611328125e-06s
INFO | --- Analysis for sitc-v4 took 126.88015842437744s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.9591064453125e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006458759307861328s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.25253939628601074s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.02067852020263672s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.482269287109375e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 7.152557373046875e-06s
INFO | --- Analysis for sli_galnet_rdf took 13.815841913223267s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.291534423828125e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0007143020629882812s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.28275227546691895s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.021041393280029297s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.337860107421875e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 7.867813110351562e-06s
INFO | --- Analysis for slideshare2rdf took 2.920396327972412s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.220008850097656e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.25029563903808594s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.147125244140625e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 8.106231689453125e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.8691792488098145s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.828744649887085s
Availability | VoID file availability check for Linked Stage Graph took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.24585986137390137s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0008780956268310547s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.698204040527344e-05s
Believability | Calculation of trust value for Linked Stage Graph took 7.867813110351562e-06s
INFO | --- Analysis for slod took 4.196695804595947s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 5.4836273193359375e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.26711416244506836s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.7404556274414062e-05s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.9186384677886963s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 0.6102607250213623s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0004858970642089844s
Extra | Recovery of all triples for Smart Points Of Interest @PSNC took 110.8043053150177s
Performance | Total latancy measurement for Smart Points Of Interest @PSNC took 0.9190456867218018s
Amount of data | Number of triples check for Smart Points Of Interest @PSNC took 8.379063844680786s
Interoperability | New terms check for Smart Points Of Interest @PSNC took 14.58774185180664s
Versatility | Languages check for Smart Points Of Interest @PSNC took 300.1836197376251s
Interpretability | Number of blank nodes check for Smart Points Of Interest @PSNC took 3.304610013961792s
Interpretability | RDF structures check for Smart Points Of Interest @PSNC took 0.25336694717407227s
Versatility | Serialization formats check for Smart Points Of Interest @PSNC took 9.521718502044678s
Availability | RDF dump link check for Smart Points Of Interest @PSNC took 0.2884337902069092s
License | MR license check for Smart Points Of Interest @PSNC took 0.4790663719177246s
License | HR license check for Smart Points Of Interest @PSNC took 300.2385070323944s
Amount of data | Number of property check for Smart Points Of Interest @PSNC took 0.3221256732940674s
Understandability | Number of label check for Smart Points Of Interest @PSNC took 2.3621485233306885s
Understandability | URI regex check for Smart Points Of Interest @PSNC took 0.5982258319854736s
Understandability | Vocabs check for Smart Points Of Interest @PSNC took 0.29189038276672363s
Verifiability | Authors check for Smart Points Of Interest @PSNC took 0.18686199188232422s
Verifiability | Publishers check for Smart Points Of Interest @PSNC took 0.258650541305542s
Performance | Throughput check for Smart Points Of Interest @PSNC took 11.476788520812988s
Amount of data | Check the number of entities for Smart Points Of Interest @PSNC took 6.365776062011719e-05s
Verifiability | Contribs. check for Smart Points Of Interest @PSNC took 0.1983177661895752s
Interlinking | sameAs chians check for Smart Points Of Interest @PSNC took 0.1940464973449707s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.5247189998626709s
Interlinking | skos check for Smart Points Of Interest @PSNC took 0.42734766006469727s
Timeliness | dataset update frequency check for Smart Points Of Interest @PSNC took 5.435730457305908s
Currency | Creation date check for Smart Points Of Interest @PSNC took 0.481870174407959s
Currency | Modification date check for Smart Points Of Interest @PSNC took 0.24062132835388184s
Rep.Conc. | URIs length for Smart Points Of Interest @PSNC took 161.57014966011047s
Interoperability | New vocabularies check for Smart Points Of Interest @PSNC took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Smart Points Of Interest @PSNC took 0.18254923820495605s
Accuracy | Check Functional Property for Smart Points Of Interest @PSNC took 0.255840539932251s
Accuracy | Check Inverse Functional Property for Smart Points Of Interest @PSNC took 0.24071741104125977s
Accuracy | Check Empty annotation labels for Smart Points Of Interest @PSNC took 38.36038064956665s
Accuracy | Check White space in annotation for Smart Points Of Interest @PSNC took 2.71923565864563s
Accuracy | Check Datatype consistency for Smart Points Of Interest @PSNC took 2.63071870803833s
Consistency | Disjoint class check for Smart Points Of Interest @PSNC took 0.2567102909088135s
Consistency | Check Misplaced properties for Smart Points Of Interest @PSNC took 81.21703720092773s
Consistency | Misplaced classes for Smart Points Of Interest @PSNC took 8.451027154922485s
Consistency | Check Ontology hijacking for Smart Points Of Interest @PSNC took 41.61659216880798s
Consistency | Check Invalid usage of undefined classes for Smart Points Of Interest @PSNC took 1.4054322242736816s
Consistency | Check Invalid usage of undefined properties for Smart Points Of Interest @PSNC took 84.55958104133606s
Conciseness | Check Extensional conciseness for Smart Points Of Interest @PSNC took 2.7251980304718018s
Conciseness | Check Intensional conciseness for Smart Points Of Interest @PSNC took 0.5869424343109131s
Security | Sign check for Smart Points Of Interest @PSNC took 0.6871650218963623s
Availability | Check URIs Dereferenciability for Smart Points Of Interest @PSNC took 10.16590690612793s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.39407944679260254s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.020830869674682617s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 0.00010347366333007812s
Interoperability | Check the re-using of existing vocabs for Smart Points Of Interest @PSNC took 2.1457672119140625e-06s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 6.67572021484375e-06s
INFO | --- Analysis for Smart_POI_dataset took 2257.3559863567352s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 6.076600790023804s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0007345676422119141s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.29337573051452637s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020774126052856445s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.814697265625e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 8.106231689453125e-06s
INFO | --- Analysis for smartlink took 15.563652276992798s
Availability | SPARQL endpoint availability check for SNIK took 0.443068265914917s
Availability | VoID file availability check for SNIK took 0.0007059574127197266s
Extra | Recovery of all triples for SNIK took 8.09088945388794s
Performance | Total latancy measurement for SNIK took 0.9454014301300049s
Amount of data | Number of triples check for SNIK took 0.19886517524719238s
Interoperability | New terms check for SNIK took 1.4716293811798096s
Versatility | Languages check for SNIK took 0.2323141098022461s
Interpretability | Number of blank nodes check for SNIK took 0.18452143669128418s
Interpretability | RDF structures check for SNIK took 0.19957280158996582s
Versatility | Serialization formats check for SNIK took 0.2132720947265625s
Availability | RDF dump link check for SNIK took 0.1968977451324463s
License | MR license check for SNIK took 0.2315535545349121s
License | HR license check for SNIK took 0.21703863143920898s
Amount of data | Number of property check for SNIK took 0.1990208625793457s
Understandability | Number of label check for SNIK took 0.19205021858215332s
Understandability | URI regex check for SNIK took 0.4045534133911133s
Understandability | Vocabs check for SNIK took 0.19768595695495605s
Verifiability | Authors check for SNIK took 0.19865846633911133s
Verifiability | Publishers check for SNIK took 0.20776581764221191s
Performance | Throughput check for SNIK took 11.211173057556152s
Amount of data | Check the number of entities for SNIK took 7.43865966796875e-05s
Verifiability | Contribs. check for SNIK took 0.20800185203552246s
Interlinking | sameAs chians check for SNIK took 0.21098661422729492s
Interlinking | skos check for SNIK took 0.1976320743560791s
Interlinking | skos check for SNIK took 0.1968986988067627s
Timeliness | dataset update frequency check for SNIK took 0.199019193649292s
Currency | Creation date check for SNIK took 0.39426398277282715s
Currency | Modification date check for SNIK took 0.39447736740112305s
Rep.Conc. | URIs length for SNIK took 1.8904573917388916s
Interoperability | New vocabularies check for SNIK took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for SNIK took 0.20673847198486328s
Accuracy | Check Functional Property for SNIK took 0.2060377597808838s
Accuracy | Check Inverse Functional Property for SNIK took 0.21279025077819824s
Accuracy | Check Empty annotation labels for SNIK took 0.7718682289123535s
Accuracy | Check White space in annotation for SNIK took 0.027286291122436523s
Accuracy | Check Datatype consistency for SNIK took 0.22327327728271484s
Consistency | Disjoint class check for SNIK took 0.20511484146118164s
Consistency | Check Misplaced properties for SNIK took 0.6814980506896973s
Consistency | Misplaced classes for SNIK took 0.7011396884918213s
Consistency | Check Ontology hijacking for SNIK took 1.8590331077575684s
Consistency | Check Invalid usage of undefined classes for SNIK took 1.3197541236877441s
Consistency | Check Invalid usage of undefined properties for SNIK took 1.5998685359954834s
Conciseness | Check Extensional conciseness for SNIK took 0.15155434608459473s
Conciseness | Check Intensional conciseness for SNIK took 0.3434762954711914s
Security | Sign check for SNIK took 0.18901634216308594s
Availability | Check URIs Dereferenciability for SNIK took 768.7038300037384s
Completeness | Calculation of interlinking completeness for SNIK took 0.4531080722808838s
Reputation | Calculation of the PageRank for SNIK took 0.02295827865600586s
Interlinking | Calculation of Degree of Connection for SNIK took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for SNIK took 0.00014781951904296875s
Interoperability | Check the re-using of existing vocabs for SNIK took 1.1920928955078125e-06s
Believability | Calculation of trust value for SNIK took 7.62939453125e-06s
INFO | --- Analysis for snik took 828.8696179389954s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.458427429199219e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.7000589370727539s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.02080059051513672s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007843971252441406s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 1.2874603271484375e-05s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 4.765895843505859s
Availability | SPARQL endpoint availability check for SocialLink took 1.2078306674957275s
Availability | VoID file availability check for SocialLink took 0.0006532669067382812s
Completeness | Calculation of interlinking completeness for SocialLink took 0.27576160430908203s
Reputation | Calculation of the PageRank for SocialLink took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007936954498291016s
Interlinking | Calculation of Clustering coefficient for SocialLink took 8.130073547363281e-05s
Believability | Calculation of trust value for SocialLink took 7.62939453125e-06s
INFO | --- Analysis for SocialLink took 5.783194303512573s
Availability | SPARQL endpoint availability check for SocialLink took 4.363059997558594e-05s
Availability | VoID file availability check for SocialLink took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for SocialLink took 0.2674129009246826s
Reputation | Calculation of the PageRank for SocialLink took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.147125244140625e-05s
Believability | Calculation of trust value for SocialLink took 8.344650268554688e-06s
INFO | --- Analysis for sociallink took 2.8991737365722656s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.4345855712890625e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.273700475692749s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.147125244140625e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 7.152557373046875e-06s
INFO | --- Analysis for SocialRoles took 11.223585844039917s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 0.3113992214202881s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.0007224082946777344s
Extra | Recovery of all triples for Social Semantic Web Thesaurus took 23.334590196609497s
Performance | Total latancy measurement for Social Semantic Web Thesaurus took 0.4903378486633301s
Amount of data | Number of triples check for Social Semantic Web Thesaurus took 0.2281475067138672s
Interoperability | New terms check for Social Semantic Web Thesaurus took 1.5616717338562012s
Versatility | Languages check for Social Semantic Web Thesaurus took 0.39609336853027344s
Interpretability | Number of blank nodes check for Social Semantic Web Thesaurus took 0.20247554779052734s
Security | Check HTTPS for Social Semantic Web Thesaurus took 0.36228251457214355s
Interpretability | RDF structures check for Social Semantic Web Thesaurus took 0.11878252029418945s
Versatility | Serialization formats check for Social Semantic Web Thesaurus took 0.13503766059875488s
Availability | RDF dump link check for Social Semantic Web Thesaurus took 0.8370718955993652s
License | MR license check for Social Semantic Web Thesaurus took 0.11508798599243164s
License | HR license check for Social Semantic Web Thesaurus took 0.11247849464416504s
Amount of data | Number of property check for Social Semantic Web Thesaurus took 0.11435055732727051s
Understandability | Number of label check for Social Semantic Web Thesaurus took 0.14102768898010254s
Understandability | URI regex check for Social Semantic Web Thesaurus took 0.20481634140014648s
Understandability | Vocabs check for Social Semantic Web Thesaurus took 0.10370731353759766s
Verifiability | Authors check for Social Semantic Web Thesaurus took 0.12658929824829102s
Verifiability | Publishers check for Social Semantic Web Thesaurus took 0.11119508743286133s
Performance | Throughput check for Social Semantic Web Thesaurus took 10.524718761444092s
Amount of data | Check the number of entities for Social Semantic Web Thesaurus took 7.510185241699219e-05s
Verifiability | Contribs. check for Social Semantic Web Thesaurus took 0.11751389503479004s
Interlinking | sameAs chians check for Social Semantic Web Thesaurus took 0.1391124725341797s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11853170394897461s
Interlinking | skos check for Social Semantic Web Thesaurus took 0.11488628387451172s
Timeliness | dataset update frequency check for Social Semantic Web Thesaurus took 0.07855582237243652s
Currency | Creation date check for Social Semantic Web Thesaurus took 0.20257902145385742s
Currency | Modification date check for Social Semantic Web Thesaurus took 0.20531797409057617s
Rep.Conc. | URIs length for Social Semantic Web Thesaurus took 2.1907758712768555s
Interoperability | New vocabularies check for Social Semantic Web Thesaurus took 8.20233702659607s
Consistency | Deprecated classes/propertiers check for Social Semantic Web Thesaurus took 0.11388635635375977s
Accuracy | Check Functional Property for Social Semantic Web Thesaurus took 0.09702372550964355s
Accuracy | Check Inverse Functional Property for Social Semantic Web Thesaurus took 0.08476686477661133s
Accuracy | Check Empty annotation labels for Social Semantic Web Thesaurus took 0.5204780101776123s
Accuracy | Check White space in annotation for Social Semantic Web Thesaurus took 0.012181997299194336s
Consistency | Disjoint class check for Social Semantic Web Thesaurus took 0.08580923080444336s
Consistency | Check Misplaced properties for Social Semantic Web Thesaurus took 0.32156991958618164s
Consistency | Misplaced classes for Social Semantic Web Thesaurus took 0.09980416297912598s
Consistency | Check Ontology hijacking for Social Semantic Web Thesaurus took 2.315317153930664s
Consistency | Check Invalid usage of undefined properties for Social Semantic Web Thesaurus took 1.5061683654785156s
Conciseness | Check Extensional conciseness for Social Semantic Web Thesaurus took 0.0005428791046142578s
Security | Sign check for Social Semantic Web Thesaurus took 0.09192061424255371s
Availability | Check URIs Dereferenciability for Social Semantic Web Thesaurus took 119.54472661018372s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.3634376525878906s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.989738464355469e-05s
Interoperability | Check the re-using of existing vocabs for Social Semantic Web Thesaurus took 1.2734975814819336s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.5735626220703125e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 661.8950898647308s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2763841152191162s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0002765655517578125s
Extra | Recovery of all triples for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 119.77352118492126s
Performance | Total latancy measurement for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9422128200531006s
Amount of data | Number of triples check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.187817573547363s
Interoperability | New terms check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 13.602202415466309s
Versatility | Languages check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.19257616996765s
Interpretability | Number of blank nodes check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.020843267440796s
Interpretability | RDF structures check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2207324504852295s
Versatility | Serialization formats check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.565478086471558s
Availability | RDF dump link check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2981584072113037s
License | MR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.34712743759155273s
License | HR license check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 300.24738335609436s
Amount of data | Number of property check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3511199951171875s
Understandability | Number of label check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.288855791091919s
Understandability | URI regex check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.637908935546875s
Understandability | Vocabs check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.3978407382965088s
Verifiability | Authors check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2124323844909668s
Verifiability | Publishers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.25510382652282715s
Performance | Throughput check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 11.553472757339478s
Amount of data | Check the number of entities for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 7.605552673339844e-05s
Verifiability | Contribs. check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19642257690429688s
Interlinking | sameAs chians check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18744850158691406s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.4468259811401367s
Interlinking | skos check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.42856907844543457s
Timeliness | dataset update frequency check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 5.366819143295288s
Currency | Creation date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.47463011741638184s
Currency | Modification date check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.23578953742980957s
Rep.Conc. | URIs length for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 144.5163094997406s
Interoperability | New vocabularies check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.21357107162475586s
Accuracy | Check Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.2719407081604004s
Accuracy | Check Inverse Functional Property for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.31107282638549805s
Accuracy | Check Empty annotation labels for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 41.889602184295654s
Accuracy | Check White space in annotation for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.689260721206665s
Accuracy | Check Datatype consistency for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.621178150177002s
Consistency | Disjoint class check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.19622039794921875s
Consistency | Check Misplaced properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 82.47232747077942s
Consistency | Misplaced classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.574204444885254s
Consistency | Check Ontology hijacking for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 36.12180256843567s
Consistency | Check Invalid usage of undefined classes for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.4211065769195557s
Consistency | Check Invalid usage of undefined properties for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 84.99710607528687s
Conciseness | Check Extensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 2.7502248287200928s
Conciseness | Check Intensional conciseness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.517920970916748s
Security | Sign check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.9459145069122314s
Availability | Check URIs Dereferenciability for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 10.589030027389526s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.0375607013702393s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.9073486328125e-06s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 6.9141387939453125e-06s
INFO | --- Analysis for Soil_maps took 2252.1663389205933s
Availability | SPARQL endpoint availability check for terrorrist ontology took 5.412101745605469e-05s
Availability | VoID file availability check for terrorrist ontology took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.6983869075775146s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02117323875427246s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 3.910064697265625e-05s
Believability | Calculation of trust value for terrorrist ontology took 7.867813110351562e-06s
INFO | --- Analysis for somya_omer took 2.832939624786377s
Availability | SPARQL endpoint availability check for Sonclubcx took 4.410743713378906e-05s
Availability | VoID file availability check for Sonclubcx took 0.0006382465362548828s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.2700636386871338s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.239776611328125e-05s
Believability | Calculation of trust value for Sonclubcx took 7.3909759521484375e-06s
INFO | --- Analysis for sonclubcx took 3.8832802772521973s
Availability | SPARQL endpoint availability check for SORS took 4.5299530029296875e-05s
Availability | VoID file availability check for SORS took 0.0006544589996337891s
Completeness | Calculation of interlinking completeness for SORS took 0.2556419372558594s
Reputation | Calculation of the PageRank for SORS took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for SORS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SORS took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for SORS took 4.887580871582031e-05s
Believability | Calculation of trust value for SORS took 5.7220458984375e-06s
INFO | --- Analysis for sors took 12.98105525970459s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.363059997558594e-05s
Availability | VoID file availability check for Soudy České republiky took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.28897738456726074s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.0203397274017334s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 2.9802322387695312e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.3909759521484375e-06s
INFO | --- Analysis for soudy--esk--republiky took 2.913140058517456s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.38690185546875e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.24765896797180176s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.02073955535888672s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 8.940696716308594e-05s
Believability | Calculation of trust value for southampton-ac-uk took 6.4373016357421875e-06s
INFO | --- Analysis for southampton-ac-uk took 3.687659978866577s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 3.4314613342285156s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.0006406307220458984s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.29497599601745605s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0040740966796875e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 7.867813110351562e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 10.62959337234497s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.363059997558594e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0014476776123046875s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.2541773319244385s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.059906005859375e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 6.67572021484375e-06s
INFO | --- Analysis for southampton-ecs-eprints took 4.307074546813965s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 0.5670464038848877s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0002605915069580078s
Extra | Recovery of all triples for Spanish Linguistic Datasets took 208.94301915168762s
Performance | Total latancy measurement for Spanish Linguistic Datasets took 1.223600149154663s
Amount of data | Number of triples check for Spanish Linguistic Datasets took 2.113452672958374s
Interoperability | New terms check for Spanish Linguistic Datasets took 3.09873628616333s
Versatility | Languages check for Spanish Linguistic Datasets took 44.85811901092529s
Interpretability | Number of blank nodes check for Spanish Linguistic Datasets took 1.0739343166351318s
Security | Check HTTPS for Spanish Linguistic Datasets took 0.14572358131408691s
Interpretability | RDF structures check for Spanish Linguistic Datasets took 0.2953357696533203s
Versatility | Serialization formats check for Spanish Linguistic Datasets took 1.248708963394165s
Availability | RDF dump link check for Spanish Linguistic Datasets took 0.2743194103240967s
License | MR license check for Spanish Linguistic Datasets took 0.27574849128723145s
License | HR license check for Spanish Linguistic Datasets took 0.40778565406799316s
Amount of data | Number of property check for Spanish Linguistic Datasets took 0.2913813591003418s
Understandability | Number of label check for Spanish Linguistic Datasets took 0.3286147117614746s
Understandability | URI regex check for Spanish Linguistic Datasets took 0.5575947761535645s
Understandability | Vocabs check for Spanish Linguistic Datasets took 0.2910139560699463s
Verifiability | Authors check for Spanish Linguistic Datasets took 0.2944161891937256s
Verifiability | Publishers check for Spanish Linguistic Datasets took 0.2808847427368164s
Performance | Throughput check for Spanish Linguistic Datasets took 11.157654523849487s
Amount of data | Check the number of entities for Spanish Linguistic Datasets took 0.000110626220703125s
Verifiability | Contribs. check for Spanish Linguistic Datasets took 0.2827284336090088s
Interlinking | sameAs chians check for Spanish Linguistic Datasets took 0.27222561836242676s
Interlinking | skos check for Spanish Linguistic Datasets took 0.3056209087371826s
Interlinking | skos check for Spanish Linguistic Datasets took 0.22379708290100098s
Timeliness | dataset update frequency check for Spanish Linguistic Datasets took 0.2874128818511963s
Currency | Creation date check for Spanish Linguistic Datasets took 0.5786032676696777s
Currency | Modification date check for Spanish Linguistic Datasets took 0.573455810546875s
Rep.Conc. | URIs length for Spanish Linguistic Datasets took 75.94035243988037s
Interoperability | New vocabularies check for Spanish Linguistic Datasets took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Spanish Linguistic Datasets took 0.2981445789337158s
Accuracy | Check Functional Property for Spanish Linguistic Datasets took 0.2681901454925537s
Accuracy | Check Inverse Functional Property for Spanish Linguistic Datasets took 8.37211799621582s
Accuracy | Check Empty annotation labels for Spanish Linguistic Datasets took 0.9518189430236816s
Accuracy | Check White space in annotation for Spanish Linguistic Datasets took 0.00998377799987793s
Accuracy | Check Datatype consistency for Spanish Linguistic Datasets took 2.760566473007202s
Consistency | Disjoint class check for Spanish Linguistic Datasets took 0.29303526878356934s
Consistency | Check Misplaced properties for Spanish Linguistic Datasets took 4.89862322807312s
Consistency | Misplaced classes for Spanish Linguistic Datasets took 8.521378517150879s
Consistency | Check Ontology hijacking for Spanish Linguistic Datasets took 68.72920966148376s
Consistency | Check Invalid usage of undefined classes for Spanish Linguistic Datasets took 1.445711612701416s
Consistency | Check Invalid usage of undefined properties for Spanish Linguistic Datasets took 5.755109786987305s
Conciseness | Check Extensional conciseness for Spanish Linguistic Datasets took 2.905574321746826s
Conciseness | Check Intensional conciseness for Spanish Linguistic Datasets took 0.32682251930236816s
Security | Sign check for Spanish Linguistic Datasets took 0.30732297897338867s
Availability | Check URIs Dereferenciability for Spanish Linguistic Datasets took 12.26963210105896s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.49073028564453125s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.020684242248535156s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.62396240234375e-05s
Interoperability | Check the re-using of existing vocabs for Spanish Linguistic Datasets took 1.9073486328125e-06s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 6.9141387939453125e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 512.5758917331696s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 0.07336544990539551s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.2579832077026367s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.506111145019531e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 6.9141387939453125e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.4162652492523193s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 0.00011706352233886719s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.275317907333374s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020242929458618164s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 2.765655517578125e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 6.9141387939453125e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 2.9055118560791016s
Availability | SPARQL endpoint availability check for SPQR took 5.173683166503906e-05s
Availability | VoID file availability check for SPQR took 0.0003421306610107422s
Completeness | Calculation of interlinking completeness for SPQR took 0.2520637512207031s
Reputation | Calculation of the PageRank for SPQR took 0.021178245544433594s
Interlinking | Calculation of Degree of Connection for SPQR took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SPQR took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for SPQR took 2.9802322387695312e-05s
Believability | Calculation of trust value for SPQR took 8.106231689453125e-06s
INFO | --- Analysis for spqr took 3.377061128616333s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.38690185546875e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0006313323974609375s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2709510326385498s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.020576953887939453s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.511543273925781e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 7.62939453125e-06s
INFO | --- Analysis for springernaturescigraph took 3.565502405166626s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.410743713378906e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0005965232849121094s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.255840539932251s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0203554630279541s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0007195472717285156s
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 7.152557373046875e-06s
INFO | --- Analysis for srcmf took 7.797600030899048s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 0.5969903469085693s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.2776486873626709s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020223617553710938s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.458427429199219e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 7.3909759521484375e-06s
INFO | --- Analysis for ssf took 3.831655979156494s
Availability | SPARQL endpoint availability check for SSF took 4.172325134277344e-05s
Availability | VoID file availability check for SSF took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for SSF took 0.2553284168243408s
Reputation | Calculation of the PageRank for SSF took 0.022077560424804688s
Interlinking | Calculation of Degree of Connection for SSF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SSF took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for SSF took 3.123283386230469e-05s
Believability | Calculation of trust value for SSF took 2.5033950805664062e-05s
INFO | --- Analysis for ssf-lexicon took 2.8996176719665527s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.315376281738281e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0003101825714111328s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.27712535858154297s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020799636840820312s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.361701965332031e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.1444091796875e-05s
INFO | --- Analysis for st-andrews-resource-lists took 2.718543767929077s
Availability | SPARQL endpoint availability check for STAC took 4.1484832763671875e-05s
Availability | VoID file availability check for STAC took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for STAC took 0.2655937671661377s
Reputation | Calculation of the PageRank for STAC took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for STAC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for STAC took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for STAC took 2.8133392333984375e-05s
Believability | Calculation of trust value for STAC took 7.3909759521484375e-06s
INFO | --- Analysis for stac took 2.8775131702423096s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.2438507080078125e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.24675965309143066s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007658004760742188s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 2.9087066650390625e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 7.867813110351562e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.88311767578125s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.291534423828125e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.25844478607177734s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.314018249511719e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 9.298324584960938e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 4.235827207565308s
Availability | SPARQL endpoint availability check for Stammbuch took 4.267692565917969e-05s
Availability | VoID file availability check for Stammbuch took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.23993372917175293s
Reputation | Calculation of the PageRank for Stammbuch took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Stammbuch took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Stammbuch took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.7179718017578125e-05s
Believability | Calculation of trust value for Stammbuch took 6.9141387939453125e-06s
INFO | --- Analysis for Stammbuch took 2.2641968727111816s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 1.2436535358428955s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.27755141258239746s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010347366333007812s
Believability | Calculation of trust value for statistics.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for statistics-data-gov-uk took 3.8737845420837402s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 8.392333984375e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.28383588790893555s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.86102294921875e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 1.1682510375976562e-05s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.952301502227783s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0005581378936767578s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.27526068687438965s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.020143985748291016s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-1w6-org took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.962435007095337s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 5.459785461425781e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.2610738277435303s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-20100-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-20100-org took 2.4496009349823s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0005557537078857422s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.2636396884918213s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020171403884887695s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.723403930664062e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.741520404815674s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.26363682746887207s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.867813110351562e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.5935235023498535s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0003383159637451172s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.2722632884979248s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.0201416015625s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.893013000488281e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.526599645614624s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.0005786418914794922s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.294475793838501s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-bka-li took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-bka-li took 3.411285161972046s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.27123355865478516s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02056741714477539s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 4.00543212890625e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 3.315453052520752s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 5.14984130859375e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0006909370422363281s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.27026915550231934s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007500648498535156s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 5.2928924560546875e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ced117-net took 3.8715176582336426s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0005421638488769531s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.2574422359466553s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020313501358032227s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.525251865386963s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 5.1975250244140625e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.24978017807006836s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.02028369903564453s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.000110626220703125s
Believability | Calculation of trust value for statusnet-chromic-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-chromic-org took 2.5195555686950684s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0006721019744873047s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2624168395996094s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020978689193725586s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0009434223175048828s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 9.226799011230469e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 5.872824430465698s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.2797667980194092s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02065277099609375s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.4163219928741455s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.7206878662109375e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005586147308349609s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.25460147857666016s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020493745803833008s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.771087646484375e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 3.189723491668701s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.2719457149505615s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.020662784576416016s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010251998901367188s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 7.62939453125e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.6385602951049805s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.25072479248046875s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0008165836334228516s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.628036499023438e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.3943681716918945s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 5.245208740234375e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0003666877746582031s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.2785451412200928s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.0211026668548584s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0008530616760253906s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-doomicile-de took 3.295915365219116s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.2749521732330322s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.984306335449219e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-dtdns-net took 22.353623390197754s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.2698788642883301s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.24249267578125e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.4471242427825928s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0008223056793212891s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.28386998176574707s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.020745277404785156s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.200241088867188e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-exdc-net took 12.569712400436401s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0006513595581054688s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.27811360359191895s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020552635192871094s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.34600830078125e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-fcac-com took 22.37842345237732s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2582573890686035s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 3.433688163757324s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.001329183578491211s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.24539470672607422s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0001895427703857422s
Believability | Calculation of trust value for statusnet-fragdev-com took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-fragdev-com took 3.2512850761413574s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0005922317504882812s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.26242923736572266s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.451594829559326s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2833268642425537s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.0001087188720703125s
Believability | Calculation of trust value for statusnet-gegeweb-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.5441176891326904s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2723989486694336s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020570755004882812s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.890296936035156e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-glou-org took 2.471909761428833s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.2628364562988281s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020543336868286133s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00013756752014160156s
Believability | Calculation of trust value for statusnet-gomertronic-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.3687095642089844s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 7.987022399902344e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.2875709533691406s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020568370819091797s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010585784912109375s
Believability | Calculation of trust value for statusnet-hackerposse-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 3.0086588859558105s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 4.792213439941406e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0006144046783447266s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.26210737228393555s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.57763671875e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-hii-co-il took 3.7355291843414307s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0009815692901611328s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.2760128974914551s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020585060119628906s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.322166442871094e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 3.4715375900268555s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0006346702575683594s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.2400960922241211s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02082991600036621s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 6.699562072753906e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 2.535522699356079s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 6.127357482910156e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0006186962127685547s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2673804759979248s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.100799560546875e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.548926591873169s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0006420612335205078s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.26763486862182617s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.3882598876953125e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 22.417799949645996s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0005371570587158203s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.2568809986114502s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007655620574951172s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00011515617370605469s
Believability | Calculation of trust value for statusnet-jonkman-ca took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 3.204636573791504s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.2830185890197754s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.703636169433594e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-kaimi-cc took 2.4176673889160156s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.26244211196899414s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.02046656608581543s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.839897155761719e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-kathryl-fr took 2.4038753509521484s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.0005319118499755859s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.26326608657836914s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 3.2650468349456787s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.27770042419433594s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020395517349243164s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 7.200241088867188e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.4391636848449707s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.26636171340942383s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.673004150390625e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.4953086376190186s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.26642680168151855s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.02001333236694336s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.5918567180633545s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.2761826515197754s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020362377166748047s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.512901306152344e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.6458704471588135s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.000759124755859375s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2650129795074463s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011873245239257812s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.454038143157959s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0005502700805664062s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.25510668754577637s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020340919494628906s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 5.7220458984375e-06s
INFO | --- Analysis for statusnet-ludost-net took 3.8631036281585693s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.291534423828125e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.2714405059814453s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.560585021972656e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.406339406967163s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.29372143745422363s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 3.5193662643432617s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 7.605552673339844e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2666337490081787s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.022632598876953125s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0010809898376464844s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00018668174743652344s
Believability | Calculation of trust value for statusnet-macno-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-macno-org took 2.453488826751709s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.2682061195373535s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.02020406723022461s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.365776062011719e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.458803176879883s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 5.221366882324219e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0006554126739501953s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.313443660736084s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02105116844177246s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.273124694824219e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-maymay-net took 42.0997576713562s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 9.34600830078125e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0005404949188232422s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.27812838554382324s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02113199234008789s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001666545867919922s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.4304065704345703s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0006196498870849609s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.27864623069763184s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.021552324295043945s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 0.0001010894775390625s
Believability | Calculation of trust value for statusnet-mrblog-nl took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.503119945526123s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0010952949523925781s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.25865697860717773s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020954132080078125s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 6.0558319091796875e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.3882789611816406s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.270277738571167s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.550473690032959s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2826650142669678s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007698535919189453s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.0001163482666015625s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.8596649169921875e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.542426347732544s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0006289482116699219s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.25059938430786133s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.841255187988281e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.56268572807312s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 5.1021575927734375e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.23966741561889648s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0008416175842285156s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.842613220214844e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.4987478256225586s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 5.698204040527344e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0006012916564941406s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.265230655670166s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007505416870117188s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.702278137207031e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.774944305419922s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 5.9604644775390625e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2547154426574707s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020735740661621094s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.9591064453125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.62939453125e-06s
INFO | --- Analysis for statusnet-panda-id-au took 2.8514673709869385s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.27466273307800293s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020427465438842773s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.775161743164062e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 7.62939453125e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.47975492477417s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.270643949508667s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0009698867797851562s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 8.96453857421875e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.4943184852600098s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.2675645351409912s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002353191375732422s
Believability | Calculation of trust value for statusnet-postblue-info took 7.62939453125e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.460707187652588s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.744529724121094e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0005762577056884766s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.2810337543487549s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.461143493652344e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-progval-net took 2.5548858642578125s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 6.890296936035156e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0006029605865478516s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.2867579460144043s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011205673217773438s
Believability | Calculation of trust value for statusnet-qdnx-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.833312511444092s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0005686283111572266s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.27059364318847656s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 7.200241088867188e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-qth-fr took 3.2273850440979004s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0005724430084228516s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.24718880653381348s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020995378494262695s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00023698806762695312s
Believability | Calculation of trust value for statusnet-quitter-se took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.566145420074463s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.26454925537109375s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00010061264038085938s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.5873024463653564s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.5299530029296875e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.24161839485168457s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-recit-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-recit-org took 4.155198812484741s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.261871337890625s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020792722702026367s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.0001494884490966797s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-russwurm-org took 3.197892427444458s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0003418922424316406s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.2579779624938965s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020588159561157227s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-samnoble-org took 4.787066221237183s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005507469177246094s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.26718616485595703s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0009381771087646484s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 9.822845458984375e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.5168814659118652s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.27960753440856934s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.894371032714844e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.4604101181030273s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.2571706771850586s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020767927169799805s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007607936859130859s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.532669067382812e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.5573439598083496s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0006148815155029297s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.2741522789001465s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.43865966796875e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 3.363342046737671s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0007922649383544922s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.29013848304748535s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0009822845458984375s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00023603439331054688s
Believability | Calculation of trust value for statusnet-skilledtests-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 3.027505397796631s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.2843201160430908s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020717144012451172s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0009474754333496094s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00012183189392089844s
Believability | Calculation of trust value for statusnet-somsants-net took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.378526210784912s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.25209951400756836s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.02413654327392578s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0009491443634033203s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.0001800060272216797s
Believability | Calculation of trust value for statusnet-soucy-cc took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.4110803604125977s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.553794860839844e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0006036758422851562s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.3075902462005615s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-spip-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-spip-org took 3.404231548309326s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.601478576660156e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.2939009666442871s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.02065753936767578s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.556510925292969e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.3719565868377686s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2567574977874756s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020584821701049805s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0007581710815429688s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010967254638671875s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 5.561320066452026s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0005400180816650391s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.2612266540527344s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00023031234741210938s
Believability | Calculation of trust value for statusnet-status-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-status-net took 3.682675838470459s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.38690185546875e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.26340436935424805s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020848512649536133s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.888938903808594e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.3815670013427734s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.3392181396484375e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0006561279296875s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.2744731903076172s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020152568817138672s
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.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.1552734375e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 3.0606749057769775s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.458427429199219e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.23979687690734863s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.00012826919555664062s
Believability | Calculation of trust value for statusnet-thelovebug-org took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.300555944442749s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.000659942626953125s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.2518801689147949s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.557868957519531e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 9.059906005859375e-06s
INFO | --- Analysis for statusnet-thornton2-com took 5.115171909332275s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 4.506111145019531e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0006253719329833984s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2556328773498535s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020471811294555664s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.0001087188720703125s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.6989920139312744s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0006794929504394531s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.28775835037231445s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020640850067138672s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007596015930175781s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.647804260253906e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 3.5138256549835205s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.410743713378906e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.2622969150543213s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.6482558250427246s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.2704756259918213s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.9577484130859375e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.5242836475372314s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.267692565917969e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0005908012390136719s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.2686493396759033s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.020615100860595703s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for steak took 3.573439121246338s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 4.458427429199219e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2646293640136719s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.7697296142578125e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 6.67572021484375e-06s
INFO | --- Analysis for stitch-rameau took 3.9936366081237793s
Availability | SPARQL endpoint availability check for Stone Tech Square took 0.7840189933776855s
Availability | VoID file availability check for Stone Tech Square took 0.000644683837890625s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.27916455268859863s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020482778549194336s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.2874603271484375e-05s
Believability | Calculation of trust value for Stone Tech Square took 1.2159347534179688e-05s
INFO | --- Analysis for stone-tech-square-data took 5.219856262207031s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.4345855712890625e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.27987146377563477s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 2.9087066650390625e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.152557373046875e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 2.849076747894287s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 349.8138015270233s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.0007827281951904297s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.2989997863769531s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.02101445198059082s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00012946128845214844s
Believability | Calculation of trust value for STW Thesaurus for Economics took 7.152557373046875e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 808.3648011684418s
Availability | SPARQL endpoint availability check for SudershanTech took 4.2438507080078125e-05s
Availability | VoID file availability check for SudershanTech took 0.0002186298370361328s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.28163933753967285s
Reputation | Calculation of the PageRank for SudershanTech took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for SudershanTech took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007569789886474609s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 2.8371810913085938e-05s
Believability | Calculation of trust value for SudershanTech took 6.198883056640625e-06s
INFO | --- Analysis for SudershanTech took 2.4547696113586426s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 0.9437663555145264s
Availability | VoID file availability check for Sudoc bibliographic data took 0.0005681514739990234s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.27771449089050293s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.5299530029296875e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.1920928955078125e-05s
INFO | --- Analysis for sudocfr took 7.817495346069336s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 1.0120346546173096s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0006155967712402344s
Extra | Recovery of all triples for Suface Forestière Mondiale 1990-2016 took 288.3551986217499s
Performance | Total latancy measurement for Suface Forestière Mondiale 1990-2016 took 2.7010836601257324s
Amount of data | Number of triples check for Suface Forestière Mondiale 1990-2016 took 1.5251612663269043s
Interoperability | New terms check for Suface Forestière Mondiale 1990-2016 took 3.046673059463501s
Versatility | Languages check for Suface Forestière Mondiale 1990-2016 took 3.565751791000366s
Interpretability | Number of blank nodes check for Suface Forestière Mondiale 1990-2016 took 1.2259602546691895s
Interpretability | RDF structures check for Suface Forestière Mondiale 1990-2016 took 0.5667693614959717s
Versatility | Serialization formats check for Suface Forestière Mondiale 1990-2016 took 0.5523977279663086s
Availability | RDF dump link check for Suface Forestière Mondiale 1990-2016 took 0.5338070392608643s
License | MR license check for Suface Forestière Mondiale 1990-2016 took 0.5462579727172852s
License | HR license check for Suface Forestière Mondiale 1990-2016 took 7.806762933731079s
Amount of data | Number of property check for Suface Forestière Mondiale 1990-2016 took 0.5727972984313965s
Understandability | Number of label check for Suface Forestière Mondiale 1990-2016 took 0.6922240257263184s
Understandability | URI regex check for Suface Forestière Mondiale 1990-2016 took 1.0829856395721436s
Understandability | Vocabs check for Suface Forestière Mondiale 1990-2016 took 0.5303812026977539s
Verifiability | Authors check for Suface Forestière Mondiale 1990-2016 took 0.5317668914794922s
Verifiability | Publishers check for Suface Forestière Mondiale 1990-2016 took 0.5528616905212402s
Performance | Throughput check for Suface Forestière Mondiale 1990-2016 took 10.921139001846313s
Amount of data | Check the number of entities for Suface Forestière Mondiale 1990-2016 took 8.678436279296875e-05s
Verifiability | Contribs. check for Suface Forestière Mondiale 1990-2016 took 0.5272073745727539s
Interlinking | sameAs chians check for Suface Forestière Mondiale 1990-2016 took 0.5397627353668213s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.6208605766296387s
Interlinking | skos check for Suface Forestière Mondiale 1990-2016 took 0.5874066352844238s
Timeliness | dataset update frequency check for Suface Forestière Mondiale 1990-2016 took 0.5755770206451416s
Currency | Creation date check for Suface Forestière Mondiale 1990-2016 took 1.1071200370788574s
Currency | Modification date check for Suface Forestière Mondiale 1990-2016 took 1.1137089729309082s
Rep.Conc. | URIs length for Suface Forestière Mondiale 1990-2016 took 77.71003651618958s
Interoperability | New vocabularies check for Suface Forestière Mondiale 1990-2016 took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for Suface Forestière Mondiale 1990-2016 took 0.5352456569671631s
Accuracy | Check Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5208337306976318s
Accuracy | Check Inverse Functional Property for Suface Forestière Mondiale 1990-2016 took 0.5437655448913574s
Accuracy | Check Empty annotation labels for Suface Forestière Mondiale 1990-2016 took 14.670735359191895s
Accuracy | Check White space in annotation for Suface Forestière Mondiale 1990-2016 took 0.3827478885650635s
Consistency | Disjoint class check for Suface Forestière Mondiale 1990-2016 took 0.547673225402832s
Consistency | Check Misplaced properties for Suface Forestière Mondiale 1990-2016 took 40.679563760757446s
Consistency | Misplaced classes for Suface Forestière Mondiale 1990-2016 took 11.709317922592163s
Consistency | Check Ontology hijacking for Suface Forestière Mondiale 1990-2016 took 300.44758892059326s
Consistency | Check Invalid usage of undefined properties for Suface Forestière Mondiale 1990-2016 took 30.02704691886902s
Conciseness | Check Extensional conciseness for Suface Forestière Mondiale 1990-2016 took 2.9930408000946045s
Conciseness | Check Intensional conciseness for Suface Forestière Mondiale 1990-2016 took 5.178803205490112s
Security | Sign check for Suface Forestière Mondiale 1990-2016 took 0.5703239440917969s
Availability | Check URIs Dereferenciability for Suface Forestière Mondiale 1990-2016 took 4741.639531135559s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.8113813400268555s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.020882844924926758s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 8.249282836914062e-05s
Interoperability | Check the re-using of existing vocabs for Suface Forestière Mondiale 1990-2016 took 1.9073486328125e-06s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 7.62939453125e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 8877.80810546875s
Availability | SPARQL endpoint availability check for Surge Radio took 5.5789947509765625e-05s
Availability | VoID file availability check for Surge Radio took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.6941533088684082s
Reputation | Calculation of the PageRank for Surge Radio took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.606910705566406e-05s
Believability | Calculation of trust value for Surge Radio took 9.059906005859375e-06s
INFO | --- Analysis for surge-radio took 6.542059421539307s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 4.2438507080078125e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0006563663482666016s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.7312018871307373s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.02031421661376953s
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.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 3.7670135498046875e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 6.67572021484375e-06s
INFO | --- Analysis for SWAT took 21.983545780181885s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.3392181396484375e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.43677520751953125s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.2393488883972168s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for Swedish Open Cultural Heritage took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Swedish Open Cultural Heritage took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 6.723403930664062e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 5.9604644775390625e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 6.0693440437316895s
Availability | SPARQL endpoint availability check for SweFN-RDF took 1.1187870502471924s
Availability | VoID file availability check for SweFN-RDF took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.28053998947143555s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020036935806274414s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.457069396972656e-05s
Believability | Calculation of trust value for SweFN-RDF took 6.198883056640625e-06s
INFO | --- Analysis for swefn-rdf took 5.69915771484375s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.1961669921875e-05s
Availability | VoID file availability check for SwetoDblp took 0.0006282329559326172s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.26383090019226074s
Reputation | Calculation of the PageRank for SwetoDblp took 0.0202786922454834s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.4809112548828125e-05s
Believability | Calculation of trust value for SwetoDblp took 6.198883056640625e-06s
INFO | --- Analysis for sweto-dblp took 22.733307600021362s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 0.5277976989746094s
Availability | VoID file availability check for Swift Vocabulary took 0.0006115436553955078s
Extra | Recovery of all triples for Swift Vocabulary took 2.3864498138427734s
Performance | Total latancy measurement for Swift Vocabulary took 0.9013388156890869s
Amount of data | Number of triples check for Swift Vocabulary took 0.16605854034423828s
Interoperability | New terms check for Swift Vocabulary took 1.4174268245697021s
Versatility | Languages check for Swift Vocabulary took 0.17525100708007812s
Interpretability | Number of blank nodes check for Swift Vocabulary took 0.18680453300476074s
Interpretability | RDF structures check for Swift Vocabulary took 0.1920931339263916s
Versatility | Serialization formats check for Swift Vocabulary took 0.19266533851623535s
Availability | RDF dump link check for Swift Vocabulary took 0.17461562156677246s
License | MR license check for Swift Vocabulary took 0.19579291343688965s
License | HR license check for Swift Vocabulary took 0.19080519676208496s
Amount of data | Number of property check for Swift Vocabulary took 0.1584153175354004s
Understandability | Number of label check for Swift Vocabulary took 0.1915595531463623s
Understandability | URI regex check for Swift Vocabulary took 0.3299727439880371s
Understandability | Vocabs check for Swift Vocabulary took 0.15979576110839844s
Verifiability | Authors check for Swift Vocabulary took 0.176544189453125s
Verifiability | Publishers check for Swift Vocabulary took 0.16001296043395996s
Performance | Throughput check for Swift Vocabulary took 10.559909343719482s
Amount of data | Check the number of entities for Swift Vocabulary took 7.128715515136719e-05s
Verifiability | Contribs. check for Swift Vocabulary took 0.23019194602966309s
Interlinking | sameAs chians check for Swift Vocabulary took 0.23145103454589844s
Interlinking | skos check for Swift Vocabulary took 0.20849871635437012s
Interlinking | skos check for Swift Vocabulary took 0.19022822380065918s
Timeliness | dataset update frequency check for Swift Vocabulary took 0.2391223907470703s
Currency | Creation date check for Swift Vocabulary took 0.4126603603363037s
Currency | Modification date check for Swift Vocabulary took 0.44489383697509766s
Rep.Conc. | URIs length for Swift Vocabulary took 0.7788698673248291s
Interoperability | New vocabularies check for Swift Vocabulary took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Swift Vocabulary took 0.15677428245544434s
Accuracy | Check Functional Property for Swift Vocabulary took 0.20887160301208496s
Accuracy | Check Inverse Functional Property for Swift Vocabulary took 0.2384929656982422s
Accuracy | Check Empty annotation labels for Swift Vocabulary took 0.37204647064208984s
Accuracy | Check White space in annotation for Swift Vocabulary took 0.0032460689544677734s
Accuracy | Check Datatype consistency for Swift Vocabulary took 0.03795504570007324s
Consistency | Disjoint class check for Swift Vocabulary took 0.18853163719177246s
Consistency | Check Misplaced properties for Swift Vocabulary took 0.4425086975097656s
Consistency | Misplaced classes for Swift Vocabulary took 0.30544114112854004s
Consistency | Check Ontology hijacking for Swift Vocabulary took 1.5911970138549805s
Consistency | Check Invalid usage of undefined classes for Swift Vocabulary took 1.3158833980560303s
Consistency | Check Invalid usage of undefined properties for Swift Vocabulary took 1.4934031963348389s
Conciseness | Check Extensional conciseness for Swift Vocabulary took 0.026805400848388672s
Conciseness | Check Intensional conciseness for Swift Vocabulary took 0.15701675415039062s
Security | Sign check for Swift Vocabulary took 0.18945527076721191s
Availability | Check URIs Dereferenciability for Swift Vocabulary took 999.3891172409058s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.5756924152374268s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020928382873535156s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.677078247070312e-05s
Interoperability | Check the re-using of existing vocabs for Swift Vocabulary took 2.1457672119140625e-06s
Believability | Calculation of trust value for Swift Vocabulary took 8.344650268554688e-06s
INFO | --- Analysis for Swift took 1045.6728429794312s
Availability | SPARQL endpoint availability check for SymbolicData took 4.220008850097656e-05s
Availability | VoID file availability check for SymbolicData took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.3146848678588867s
Reputation | Calculation of the PageRank for SymbolicData took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 2.8133392333984375e-05s
Believability | Calculation of trust value for SymbolicData took 7.62939453125e-06s
INFO | --- Analysis for symbolicdata took 4.802631616592407s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 4.363059997558594e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0008568763732910156s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.71933913230896s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 2.8848648071289062e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 6.9141387939453125e-06s
INFO | --- Analysis for symptoms-in-chinese took 54.77504277229309s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.665546178817749s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0003533363342285156s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5463573932647705s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9256525039672852s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.245067834854126s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 21.730225324630737s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.2055833339691162s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 12.063448429107666s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.14902091026306152s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.5164427757263184s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.27312517166137695s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.2008512020111084s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.3699972629547119s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.79596996307373s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.4872157573699951s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 38.12285566329956s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3529510498046875s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.22395777702331543s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.19362401962280273s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.16934728622436523s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.583205461502075s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.414817810058594e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.7420761585235596s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.7892565727233887s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6193435192108154s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5303230285644531s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.54018235206604s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 2.9841225147247314s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.818382501602173s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 65.46230506896973s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.9073486328125e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.19076323509216309s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.2318122386932373s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0023572444915771484s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.001535654067993164s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.17706966400146484s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.92722964286804s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2575533390045166s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5967822074890137s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3066575527191162s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 47.573622941970825s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002110719680786133s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.5626497268676758s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.19959664344787598s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 12.004161596298218s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.3163442611694336s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 8.606910705566406e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.430511474609375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 8.106231689453125e-06s
INFO | --- Analysis for sztaki-lod took 746.9217567443848s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00031638145446777344s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.0006644725799560547s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.26426172256469727s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.021010398864746094s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.650520324707031e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 6.67572021484375e-06s
INFO | --- Analysis for t4gm-info took 6.889742612838745s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.5299530029296875e-05s
Availability | VoID file availability check for tags2con delicious took 0.0006453990936279297s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.9010932445526123s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020672321319580078s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 3.8623809814453125e-05s
Believability | Calculation of trust value for tags2con delicious took 6.9141387939453125e-06s
INFO | --- Analysis for tags2con-delicious took 844.6209805011749s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 263.4561700820923s
Availability | VoID file availability check for Taiwan geographic names took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.29855871200561523s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.651878356933594e-05s
Believability | Calculation of trust value for Taiwan geographic names took 7.62939453125e-06s
INFO | --- Analysis for taiwan-geographic-names took 667.4489951133728s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.7023320198059082s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.020559310913085938s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.608268737792969e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 7.152557373046875e-06s
INFO | --- Analysis for talis-openlibrary took 7.853205442428589s
Availability | SPARQL endpoint availability check for TalkBank took 4.029273986816406e-05s
Availability | VoID file availability check for TalkBank took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for TalkBank took 0.27040863037109375s
Reputation | Calculation of the PageRank for TalkBank took 0.020167827606201172s
Interlinking | Calculation of Degree of Connection for TalkBank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TalkBank took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.7179718017578125e-05s
Believability | Calculation of trust value for TalkBank took 7.62939453125e-06s
INFO | --- Analysis for talkbank took 3.290435314178467s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 0.9553837776184082s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.6894629001617432s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.00012183189392089844s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 8.344650268554688e-06s
INFO | --- Analysis for taxonconcept took 14.528314590454102s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.291534423828125e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.000335693359375s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.25099658966064453s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020462751388549805s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007650852203369141s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.559226989746094e-05s
Believability | Calculation of trust value for taxonconcept-assets took 6.67572021484375e-06s
INFO | --- Analysis for taxonconcept-assets took 3.407907724380493s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 4.7206878662109375e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.26781439781188965s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.030632019042969e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 6.9141387939453125e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.8540587425231934s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 1.8093187808990479s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0006542205810546875s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.28291773796081543s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.887580871582031e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 7.3909759521484375e-06s
INFO | --- Analysis for taxref-ld took 6.746103048324585s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 261.5841944217682s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0006837844848632812s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.24171733856201172s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020806074142456055s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.62396240234375e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 7.152557373046875e-06s
INFO | --- Analysis for tcga took 540.0030171871185s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 0.33178138732910156s
Availability | VoID file availability check for TCGA Roadmap took 0.0006861686706542969s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.2738475799560547s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.02211475372314453s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.43865966796875e-05s
Believability | Calculation of trust value for TCGA Roadmap took 6.9141387939453125e-06s
INFO | --- Analysis for tcga-roadmap took 7.87434983253479s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 4.057082653045654s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0007045269012451172s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.6919674873352051s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020541667938232422s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 0.00011444091796875s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for tcmgenedit_dataset took 143.52298378944397s
Availability | SPARQL endpoint availability check for TDS took 6.723403930664062e-05s
Availability | VoID file availability check for TDS took 0.00039005279541015625s
Completeness | Calculation of interlinking completeness for TDS took 0.26058530807495117s
Reputation | Calculation of the PageRank for TDS took 0.020527124404907227s
Interlinking | Calculation of Degree of Connection for TDS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for TDS took 3.886222839355469e-05s
Believability | Calculation of trust value for TDS took 9.5367431640625e-06s
INFO | --- Analysis for tds took 5.1928651332855225s
Availability | SPARQL endpoint availability check for TED Talks took 4.649162292480469e-05s
Availability | VoID file availability check for TED Talks took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for TED Talks took 0.25441980361938477s
Reputation | Calculation of the PageRank for TED Talks took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.218650817871094e-05s
Believability | Calculation of trust value for TED Talks took 8.106231689453125e-06s
INFO | --- Analysis for ted-talks took 3.765040159225464s
Availability | SPARQL endpoint availability check for TEKORD took 5.8650970458984375e-05s
Availability | VoID file availability check for TEKORD took 0.000629425048828125s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2631404399871826s
Reputation | Calculation of the PageRank for TEKORD took 0.020468950271606445s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.601478576660156e-05s
Believability | Calculation of trust value for TEKORD took 5.7220458984375e-06s
INFO | --- Analysis for tekord took 5.732975959777832s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 3.3542754650115967s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.25208163261413574s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010824203491210938s
Believability | Calculation of trust value for Telegraphis Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for telegraphis took 9.808692216873169s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.6253204345703125e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0006501674652099609s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.2638728618621826s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 7.224082946777344e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 7.3909759521484375e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 14.914951801300049s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.25697755813598633s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 2.86102294921875e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.9230940341949463s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2607278823852539s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for terminesp took 2.9732871055603027s
Availability | SPARQL endpoint availability check for Ontology took 4.4345855712890625e-05s
Availability | VoID file availability check for Ontology took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for Ontology took 0.2797067165374756s
Reputation | Calculation of the PageRank for Ontology took 0.02054762840270996s
Interlinking | Calculation of Degree of Connection for Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for Ontology took 6.67572021484375e-06s
INFO | --- Analysis for Terrorist_attack took 2.884420871734619s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 7.176399230957031e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.2685110569000244s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020325183868408203s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.075599670410156e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 7.867813110351562e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.3889825344085693s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.220008850097656e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.2765686511993408s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.02026677131652832s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007674694061279297s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.123283386230469e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 1.0728836059570312e-05s
INFO | --- Analysis for tesauro-materias-bupm took 2.980938673019409s
Availability | SPARQL endpoint availability check for Teseo took 4.1961669921875e-05s
Availability | VoID file availability check for Teseo took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Teseo took 0.28848719596862793s
Reputation | Calculation of the PageRank for Teseo took 0.02037811279296875s
Interlinking | Calculation of Degree of Connection for Teseo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Teseo took 2.956390380859375e-05s
Believability | Calculation of trust value for Teseo took 6.67572021484375e-06s
INFO | --- Analysis for teseo took 2.971004009246826s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.482269287109375e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006356239318847656s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.27138471603393555s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.02080821990966797s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.218650817871094e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 6.67572021484375e-06s
INFO | --- Analysis for Tesla_Deaths took 5.840893030166626s
Availability | SPARQL endpoint availability check for test took 4.482269287109375e-05s
Availability | VoID file availability check for test took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for test took 0.2593367099761963s
Reputation | Calculation of the PageRank for test took 0.020184755325317383s
Interlinking | Calculation of Degree of Connection for test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for test took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for test took 3.0040740966796875e-05s
Believability | Calculation of trust value for test took 6.9141387939453125e-06s
INFO | --- Analysis for test took 2.3614025115966797s
Availability | SPARQL endpoint availability check for Test took 4.482269287109375e-05s
Availability | VoID file availability check for Test took 0.00035643577575683594s
Completeness | Calculation of interlinking completeness for Test took 0.27286291122436523s
Reputation | Calculation of the PageRank for Test took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Test took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Test took 3.0279159545898438e-05s
Believability | Calculation of trust value for Test took 1.1205673217773438e-05s
INFO | --- Analysis for Test took 2.4077630043029785s
Availability | SPARQL endpoint availability check for test-svu took 20.20643949508667s
Availability | VoID file availability check for test-svu took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for test-svu took 0.2749040126800537s
Reputation | Calculation of the PageRank for test-svu took 0.020117759704589844s
Interlinking | Calculation of Degree of Connection for test-svu took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.0517578125e-05s
Believability | Calculation of trust value for test-svu took 7.3909759521484375e-06s
INFO | --- Analysis for test-svu took 52.594520568847656s
Availability | SPARQL endpoint availability check for Test took 4.553794860839844e-05s
Availability | VoID file availability check for Test took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Test took 0.26410794258117676s
Reputation | Calculation of the PageRank for Test took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for Test took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Test took 2.6702880859375e-05s
Believability | Calculation of trust value for Test took 6.9141387939453125e-06s
INFO | --- Analysis for Test_ took 2.3986520767211914s
Availability | SPARQL endpoint availability check for xxxxx took 261.72863960266113s
Availability | VoID file availability check for xxxxx took 0.0008258819580078125s
Completeness | Calculation of interlinking completeness for xxxxx took 1.3409440517425537s
Reputation | Calculation of the PageRank for xxxxx took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.57763671875e-05s
Believability | Calculation of trust value for xxxxx took 7.3909759521484375e-06s
INFO | --- Analysis for testee took 798.7875692844391s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.220008850097656e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2688276767730713s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 2.86102294921875e-05s
Believability | Calculation of trust value for Texai Lexicon took 6.198883056640625e-06s
INFO | --- Analysis for texai_lexicon took 4.765207767486572s
Availability | SPARQL endpoint availability check for tharawat magazine took 6.008148193359375e-05s
Availability | VoID file availability check for tharawat magazine took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.2651355266571045s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00012254714965820312s
Believability | Calculation of trust value for tharawat magazine took 1.2636184692382812e-05s
INFO | --- Analysis for tharawat-magazine-com took 2.9685046672821045s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.363059997558594e-05s
Availability | VoID file availability check for The CIARD RING took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.27933573722839355s
Reputation | Calculation of the PageRank for The CIARD RING took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.409385681152344e-05s
Believability | Calculation of trust value for The CIARD RING took 9.775161743164062e-06s
INFO | --- Analysis for the-ciard-ring took 3.428194761276245s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 0.15690994262695312s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.27788567543029785s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 2.956390380859375e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 7.62939453125e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.6522936820983887s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.6495599746704102s
Availability | VoID file availability check for The European Library Open Dataset took 0.0006682872772216797s
Extra | Recovery of all triples for The European Library Open Dataset took 1.3342349529266357s
Performance | Total latancy measurement for The European Library Open Dataset took 1.1738488674163818s
Amount of data | Number of triples check for The European Library Open Dataset took 30.190074682235718s
Versatility | Languages check for The European Library Open Dataset took 0.3016085624694824s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.206802368164062s
Interpretability | RDF structures check for The European Library Open Dataset took 0.30460143089294434s
Versatility | Serialization formats check for The European Library Open Dataset took 0.23967385292053223s
Availability | RDF dump link check for The European Library Open Dataset took 0.25629663467407227s
License | MR license check for The European Library Open Dataset took 0.27381372451782227s
License | HR license check for The European Library Open Dataset took 0.251178503036499s
Amount of data | Number of property check for The European Library Open Dataset took 0.23922085762023926s
Understandability | Number of label check for The European Library Open Dataset took 2.6552999019622803s
Understandability | URI regex check for The European Library Open Dataset took 0.5066690444946289s
Understandability | Vocabs check for The European Library Open Dataset took 0.2783627510070801s
Verifiability | Authors check for The European Library Open Dataset took 0.24286222457885742s
Verifiability | Publishers check for The European Library Open Dataset took 0.21703648567199707s
Performance | Throughput check for The European Library Open Dataset took 11.723344802856445s
Amount of data | Check the number of entities for The European Library Open Dataset took 7.581710815429688e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.22866344451904297s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.316190242767334s
Interlinking | skos check for The European Library Open Dataset took 0.43152785301208496s
Interlinking | skos check for The European Library Open Dataset took 0.4470057487487793s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.24142861366271973s
Currency | Creation date check for The European Library Open Dataset took 0.5716023445129395s
Currency | Modification date check for The European Library Open Dataset took 0.4931643009185791s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.497326612472534s
Interoperability | New vocabularies check for The European Library Open Dataset took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.25582361221313477s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 2.0610313415527344s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.028086423873901367s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.029634714126586914s
Consistency | Disjoint class check for The European Library Open Dataset took 0.2362537384033203s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.45960235595703s
Consistency | Misplaced classes for The European Library Open Dataset took 0.31210803985595703s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.8285894393920898s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.2773637771606445s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.498209238052368s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.034441232681274414s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 0.29152488708496094s
Security | Sign check for The European Library Open Dataset took 0.28742194175720215s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 10.79288649559021s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.7327196598052979s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020550251007080078s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.413459777832031e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.430511474609375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for the-european-library-open-dataset took 402.19179463386536s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 60.05401253700256s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0006902217864990234s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.272092342376709s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 0.00010561943054199219s
Believability | Calculation of trust value for The Eurostat Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for the-eurostat-linked-data took 245.03574752807617s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 5.3882598876953125e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.2936556339263916s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.7894973754882812e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 4.33473014831543s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 4.38690185546875e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0006568431854248047s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.26227736473083496s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.02064347267150879s
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.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 0.00010132789611816406s
Believability | Calculation of trust value for The Living LOD Cloud took 6.198883056640625e-06s
INFO | --- Analysis for the-living-lod-cloud took 43.61669588088989s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 4.029273986816406e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00022125244140625s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.6882190704345703s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.6702880859375e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 7.152557373046875e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 3.3685765266418457s
Availability | SPARQL endpoint availability check for The View From took 0.08432245254516602s
Availability | VoID file availability check for The View From took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for The View From took 0.2747805118560791s
Reputation | Calculation of the PageRank for The View From took 0.020899057388305664s
Interlinking | Calculation of Degree of Connection for The View From took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for The View From took 8.249282836914062e-05s
Believability | Calculation of trust value for The View From took 7.3909759521484375e-06s
INFO | --- Analysis for the-view-from took 2.957071542739868s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.533149003982544s
Availability | VoID file availability check for Open data of Uzbekistan took 0.00069427490234375s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.33484363555908203s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 8.344650268554688e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 73.26796007156372s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 30.048573970794678s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006849765777587891s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.27704334259033203s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.021295785903930664s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 5.602836608886719e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 8.106231689453125e-06s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 102.4683780670166s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.38690185546875e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2860229015350342s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.022070884704589844s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010848045349121094s
Believability | Calculation of trust value for The Content Wrangler took 7.3909759521484375e-06s
INFO | --- Analysis for thecontentwrangler-com took 3.3554890155792236s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.100799560546875e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.27954697608947754s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 2.8133392333984375e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 1.0728836059570312e-05s
INFO | --- Analysis for thesaurus-bncf took 3.4072530269622803s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.267692565917969e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2557485103607178s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.021097898483276367s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0008389949798583984s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.170967102050781e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 6.9141387939453125e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.417262554168701s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.4668281078338623s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.26073384284973145s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02030491828918457s
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.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.605552673339844e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 6.67572021484375e-06s
INFO | --- Analysis for thesaurus-w took 4.0322794914245605s
Availability | SPARQL endpoint availability check for theses.fr took 4.2438507080078125e-05s
Availability | VoID file availability check for theses.fr took 0.0006673336029052734s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2735440731048584s
Reputation | Calculation of the PageRank for theses.fr took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for theses.fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for theses.fr took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.5299530029296875e-05s
Believability | Calculation of trust value for theses.fr took 1.1682510375976562e-05s
INFO | --- Analysis for thesesfr took 4.123928785324097s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.3392181396484375e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.26111459732055664s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020520687103271484s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.1948089599609375e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 7.152557373046875e-06s
INFO | --- Analysis for Thinkphile took 2.3467559814453125s
Availability | SPARQL endpoint availability check for ThIST took 266.0454683303833s
Availability | VoID file availability check for ThIST took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for ThIST took 0.24553298950195312s
Reputation | Calculation of the PageRank for ThIST took 0.020838022232055664s
Interlinking | Calculation of Degree of Connection for ThIST took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ThIST took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for ThIST took 9.202957153320312e-05s
Believability | Calculation of trust value for ThIST took 7.3909759521484375e-06s
INFO | --- Analysis for thist took 565.2945363521576s
Availability | SPARQL endpoint availability check for TIP took 40.040241956710815s
Availability | VoID file availability check for TIP took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for TIP took 0.2438349723815918s
Reputation | Calculation of the PageRank for TIP took 0.020972013473510742s
Interlinking | Calculation of Degree of Connection for TIP took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for TIP took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00013399124145507812s
Believability | Calculation of trust value for TIP took 7.152557373046875e-06s
INFO | --- Analysis for tip took 104.82688999176025s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 5.221366882324219e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0007839202880859375s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.7657644748687744s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.02050495147705078s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 6.9141387939453125e-06s
INFO | --- Analysis for TOPMODEL took 21.35008430480957s
Availability | SPARQL endpoint availability check for Tourpedia took 4.172325134277344e-05s
Availability | VoID file availability check for Tourpedia took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.27033090591430664s
Reputation | Calculation of the PageRank for Tourpedia took 0.020834922790527344s
Interlinking | Calculation of Degree of Connection for Tourpedia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 2.7418136596679688e-05s
Believability | Calculation of trust value for Tourpedia took 7.62939453125e-06s
INFO | --- Analysis for tourpedia took 2.955144166946411s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 3.442516803741455s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2957947254180908s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 4.649162292480469e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 7.152557373046875e-06s
INFO | --- Analysis for TP-data took 8.226793050765991s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 1.8862061500549316s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0006246566772460938s
Extra | Recovery of all triples for Trackloaded Linked Open Data took 1.6384196281433105s
Performance | Total latancy measurement for Trackloaded Linked Open Data took 2.085777521133423s
Amount of data | Number of triples check for Trackloaded Linked Open Data took 1.8848025798797607s
Interoperability | New terms check for Trackloaded Linked Open Data took 3.0314455032348633s
Versatility | Languages check for Trackloaded Linked Open Data took 1.706312656402588s
Interpretability | Number of blank nodes check for Trackloaded Linked Open Data took 1.5887417793273926s
Interpretability | RDF structures check for Trackloaded Linked Open Data took 1.765861988067627s
Versatility | Serialization formats check for Trackloaded Linked Open Data took 1.450793743133545s
Availability | RDF dump link check for Trackloaded Linked Open Data took 1.7336914539337158s
License | MR license check for Trackloaded Linked Open Data took 1.7105343341827393s
License | HR license check for Trackloaded Linked Open Data took 1.6769824028015137s
Amount of data | Number of property check for Trackloaded Linked Open Data took 1.602234125137329s
Understandability | Number of label check for Trackloaded Linked Open Data took 1.7805957794189453s
Understandability | URI regex check for Trackloaded Linked Open Data took 4.203390836715698s
Understandability | Vocabs check for Trackloaded Linked Open Data took 1.9399383068084717s
Verifiability | Authors check for Trackloaded Linked Open Data took 1.849290132522583s
Verifiability | Publishers check for Trackloaded Linked Open Data took 1.950873851776123s
Performance | Throughput check for Trackloaded Linked Open Data took 20.8055579662323s
Amount of data | Check the number of entities for Trackloaded Linked Open Data took 7.05718994140625e-05s
Verifiability | Contribs. check for Trackloaded Linked Open Data took 1.7383291721343994s
Interlinking | sameAs chians check for Trackloaded Linked Open Data took 1.680809736251831s
Interlinking | skos check for Trackloaded Linked Open Data took 1.7077898979187012s
Interlinking | skos check for Trackloaded Linked Open Data took 0.09557199478149414s
Timeliness | dataset update frequency check for Trackloaded Linked Open Data took 2.258463144302368s
Currency | Creation date check for Trackloaded Linked Open Data took 4.599533796310425s
Currency | Modification date check for Trackloaded Linked Open Data took 3.8288841247558594s
Rep.Conc. | URIs length for Trackloaded Linked Open Data took 2.9650819301605225s
Interoperability | New vocabularies check for Trackloaded Linked Open Data took 4.5299530029296875e-06s
Consistency | Deprecated classes/propertiers check for Trackloaded Linked Open Data took 0.9777095317840576s
Consistency | Disjoint class check for Trackloaded Linked Open Data took 0.6132140159606934s
Consistency | Check Ontology hijacking for Trackloaded Linked Open Data took 0.8154036998748779s
Consistency | Check Invalid usage of undefined properties for Trackloaded Linked Open Data took 2.187727689743042s
Security | Sign check for Trackloaded Linked Open Data took 0.8303470611572266s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.26837849617004395s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.020523548126220703s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.239776611328125e-05s
Interoperability | Check the re-using of existing vocabs for Trackloaded Linked Open Data took 2.384185791015625e-06s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 7.152557373046875e-06s
